Save and resume work

Current status: partial declared journal and owner-authored handoff records. Checkpoints, restoration, and cross-agent continuation are still absent; the complete continuity acceptance gate remains open.

The four continuity layers

• Repository: pinned base, worktree delta, staged state, files, tests, and selected artifacts form a content-addressed checkpoint.
• Environment: image, tools, locks, dependency caches, declared services, and setup results form a prepared-state manifest.
• Task: goals, constraints, decisions, completed steps, failures, remaining work, files, checks, evidence, and next action form a typed Work Journal.
• Provider: an encrypted opaque session reference and native resume metadata may optimize same-provider continuation where supported.

Hidden model reasoning cannot be captured or transferred exactly. Agent-authored notes are provider-reported additions, not authoritative observations.

Checkpoint, resume, fork, and fresh

Checkpoint boundaries include pinned input, environment ready, agent turn complete, checks complete, and candidate sealed. Resume validates base, policy, image, environment, and lineage compatibility. Fork creates a child Candidate at an explicit divergence. Fresh retains the task goal with a newly pinned base and environment. Restore always creates a child Run and preserves parent evidence; it is not deterministic model replay or inherited evidence attributed as new work.

Continuity storage

Retained Agent Cells keep their working context and permitted workspace state inside the Cell across Runs. Checkpoints provide recovery and portability; the Work Journal supplies attributed handoff state. The Repository Continuity Index holds separately governed knowledge for later work and does not replace the Cell's working context or transfer its authority.

The intended local metadata default is SQLite; Cloud metadata may use PostgreSQL. Content-addressed storage holds deltas, caches, artifacts, and provider records. A repository mirror holds Git objects, and an append-only ledger holds causal events. Each class has explicit retention.

Example: after a session stops, the next adapter receives the patch, failures, decisions, and next action without pretending to receive the previous model's private reasoning.

See continuity components.