Design principles

The current Aegis design is organized around a small set of principles.

Personal Model before convenience

Aegis should become more accurate about the user, the relationship, the work, and the boundaries over time. The Personal Model is not a theme layer on top of chat history. It is the durable center of the system.

State before disposable sessions

Continuity should resume from a durable State, not from whatever transcript happened to fit in the current context window. Users manage named clones as the public surface, while the system uses State internally to keep that continuity coherent.

Grounding before narrative drift

Records and Grounding keep memory and reflection tied to concrete evidence. Aegis should not treat every recollection as equally trustworthy, and it should not let long-running work decay into summary-only folklore.

Explicit memory before transcript hoarding

Useful long-term memory is curated. Aegis promotes the right material into core memory, personal knowledge, procedural memory, relationship memory, and skill affinity instead of pretending that a giant transcript is a durable system.

One supported operator path

The public product path should stay clear: install locally, configure the provider, prepare the first clone, and continue through wake. The website should explain that path well instead of exposing every internal draft or historical design layer.