Build for deployment
Every project should have a clear runtime path, configuration boundary, and deployment story.
01 / Public engineering node
AsterCosmos
The engineering home of Aster projects.
Built for systems that need to run, evolve, and be maintained. AsterCosmos is a peer organization to ESAP, sharing membership while keeping engineering work in its own public space.
02 / Systems
Products are treated as running systems, not demos.
AsterCosmos maintains the things that need to stay alive: self-hosted services, engineering foundations, management panels, and the infrastructure that lets them be deployed, observed, and modified again.
system preview
sys 01
self-hosted product systems
sys 02
developer-facing foundations
sys 03
small-team operational surfaces
03 / Infrastructure
The path from code to maintenance stays visible.
AsterCosmos exists so code, services, documentation, deployment, and ownership boundaries can be managed together instead of scattered across personal repositories.
01
runtime and deployment defaults
runtime path
02
identity, storage, monitoring, automation
runtime path
03
maintainable boundaries between projects
runtime path
04 / Archive
ESAP remains beside AsterCosmos, not underneath it.
ESAP keeps characters, timelines, worldbuilding, and creative archives. AsterCosmos keeps engineering projects, running systems, and technical entry points. They share membership while preserving separate public identities.
ESAP
Creative archive
Characters, timelines, worldbuilding.
AsterCosmos
Engineering entry
Projects, running systems, technical entries.
01shared membership and trust boundary
02separate public identities
03archives and systems cross-reference each other
05 / Operating principles
Built to be operated.
AsterCosmos projects begin with the parts that keep them alive: deployment, ownership, configuration, documentation, and the path back into maintenance.
Keep ownership visible
The organization should make projects, permissions, and maintainers easier to find, not hide complexity.
Document the running system
Documentation is not only for the first install. It is also for the person who returns six months later to repair the system.
06 / Entry points
A quiet front door for systems that are still growing.
AsterCosmos keeps engineering projects in one public place: source, runtime surfaces, maintenance boundaries, and the links back into ESAP.