Skip to main content

Continuity and SessionFrame

The product question is not only where truth lives. It is also how that truth should feel to the user as remembered, resumable, goal-aware collaboration.

The clean-slate answer is SessionFrame.

Continuity is a derived frame​

SessionFrame is the turn-scoped slice built from:

  • ProfileGraph constraints that matter now
  • WorkGraph items that are active, blocked, or deadline-shaping
  • EvidenceGraph recall selected for the current posture
  • optional ProcedureLibrary overlays that fit the work
  • current capability truth from CapabilityRegistry

SessionFrame is:

  • derived
  • rebuildable
  • disposable
  • scoped to one turn, wake, or resume path

It is not:

  • a fifth durable owner
  • a second memory store
  • a hidden place to stash mutable truth

Why the runtime needs a frame​

The durable graphs hold far more information than a single turn should see. Aegis therefore needs one deliberate selection step that answers:

  • what are we advancing now?
  • what evidence matters right now?
  • what constraints are in force?
  • what procedure, if any, is worth overlaying?
  • what should the model actually see in this call?

The default product grammar​

The user-facing continuity surface should stay plain. By default, Aegis should answer these six things succinctly:

1. Current focus​

  • what work item is active
  • what stage it is in
  • what outcome is being pursued

2. Next action​

  • the next recommended move
  • whether it is conversational, analytical, tool-using, or waiting

3. Why now​

  • the ranked rationale behind the next action
  • the blocker, deadline, dependency, or request that raised it
  • when needed, a compact replay-derived explanation of the earlier decision that still shapes this move

4. Remembered constraints​

  • profile and relationship constraints
  • workspace or artifact constraints
  • collaboration boundaries that still matter

5. Recall reasons​

  • which evidence was recalled
  • why it was recalled now
  • whether it came from session, lineage, workspace, or profile scope

6. Resume cue​

  • what should be brought back first after interruption
  • what must not be forgotten when work resumes

Default surface behavior​

Direct shell​

The shell should bias toward one compact continuity answer:

  • where we are
  • what I recommend next
  • what I am remembering that matters

It should only expand into detailed evidence, replay, or operator controls when asked.

API and console​

Structured surfaces may expose richer forms of the same projection, but they should still be backed by the same SessionFrame semantics.

Wake and resume​

Wake flows should restore:

  • the active work packet
  • the most relevant evidence with reasons
  • the most relevant constraints
  • the most useful next move or pending decision
  • the smallest replay slice needed to recover earlier decision context correctly

Wake flows should not dump the entire memory store or replay the whole prior conversation by default.

Failure modes the design avoids​

The product model is trying to prevent several bad outcomes:

  • admin-panel continuity: the user sees raw objects instead of a coherent work story
  • semantic-search continuity: the runtime recalls similar text without regard for the active work graph
  • skill-led continuity: the session feels coherent only when a skill is loaded
  • growth-led continuity: ambient progression becomes more visible than the work itself
  • resume dump: wake surfaces replay everything instead of restoring what is useful now

Where to go next​

SessionFrame depends on good recall. Continue with Retrieval, memory, and replay to see how Aegis selects and compresses evidence.