No implementation currently clears the Snapshot + Claim threshold; this is not a claim that the product lacks the capability.
Inspect coverage boundary →Session Replay and Branching
Rebuild derived session state from an append-only event log and create lineage-preserving branches without rewriting the parent run.
What feeds it, and what does it unlock?
Arrows show learning and design dependencies, not runtime data flow. Follow any node to continue through the Atlas.
Rebuild derived session state from an append-only event log and create lineage-preserving branches without rewriting the parent run.
The structured record is in the Atlas, but the L0–L4 article has not passed content review.
Snapshot implementations
An implementation enters the map only when both a snapshot and claims exist; unknowns remain visible.
No implementation currently clears the Snapshot + Claim threshold; this is not a claim that the product lacks the capability.
Inspect coverage boundary →No implementation currently clears the Snapshot + Claim threshold; this is not a claim that the product lacks the capability.
Inspect coverage boundary →No implementation currently clears the Snapshot + Claim threshold; this is not a claim that the product lacks the capability.
Inspect coverage boundary →No implementation currently clears the Snapshot + Claim threshold; this is not a claim that the product lacks the capability.
Inspect coverage boundary →No implementation currently clears the Snapshot + Claim threshold; this is not a claim that the product lacks the capability.
Inspect coverage boundary →No implementation currently clears the Snapshot + Claim threshold; this is not a claim that the product lacks the capability.
Inspect coverage boundary →The teaching-harness reference does not automatically become an architectural claim about any vendor agent.
What has actually been tested?
Formal experiments are separate from course exercises. Exercises can validate the reference implementation but cannot replace Native evidence from a real agent.
The same run produces a stable replay fingerprint and a branch at sequence 2.
python3 -m curriculum.golden verify s07-session-replayGapped sequences, mixed runs, and out-of-range forks are rejected without rewriting the parent log.
python3 -m unittest curriculum.tests.test_vertical_slice.VerticalSliceTests.test_s07_replays_and_branches -vWhich derived views must be rebuildable after a schema migration?
Where should a branch inherit artifacts by reference instead of copying them?
How should corrupted or partially durable event tails be repaired?