Skip to main content

System model

The current system-layer model is:

Step -> Loop -> Episode -> State -> Personal Model

This is the public design language we want the website and docs to reflect.

What each layer means​

  • Step records atomic events for audit, replay, recovery, and reflection.
  • Loop records one agent execution cycle.
  • Episode frames one wake window or active runtime session.
  • State keeps one continuity line durable across episodes.
  • Personal Model stores durable understanding that should outlive one State.

Supporting surfaces​

  • Record stores durable source material.
  • Grounding ties system behavior back to the source material it relied on.
  • MemoryEntry captures promoted long-term memory.
  • ReflectionProposal records candidate learning updates.
  • SkillAffinity tracks which procedures the system should prefer and refine.

Why the model matters​

This model keeps Aegis from collapsing into one endlessly growing transcript. It gives the runtime a way to resume work, preserve evidence, and evolve memory without pretending that every old message should stay equally visible forever.

For the full canonical design reference, use the repository system-design docs under docs/system-design/.