Architecture overview

The public Aegis surface is intentionally narrow. The supported product path today is:

1. install locally
2. create or confirm identity with aegis init
3. verify readiness with aegis status
4. create a named clone
5. continue the same clone through aegis wake

The public stack

• Installer: prepares the local runtime and launcher
• Launcher: exposes the aegis command
• Durable profile: stores operator and provider shape, not raw secrets
• Durable state: keeps continuity data across sessions
• CLI runtime: keeps the first-use, provider, clone, and wake flows in one shell

Why the public docs stay small

• The docs in Start Here, Use Aegis, Reference, and Help describe the supported operator path.
• The public site should stay focused on what operators can actually install, run, and troubleshoot today.

Where system design fits

The site now also includes a dedicated System Design section under Architecture. That section is meant to summarize the active clean-slate architecture in a more layered, public-facing form without turning the public docs into an archive of every internal draft.

Use it when you want to understand:

• the durable owner model
• how SessionFrame shapes continuity
• how retrieval, replay, and long-horizon memory are governed
• how learning, gateway adapters, and progression extend the same substrate

Start with System design overview.