Seal Sprint #004 and persist its graph snapshot - #10
Merged
Conversation
Session-close protocol. Documentation and state only. graph_stats.json had never been written for this sprint, so the freshness gate's structural-delta check had no current snapshot to compare against — the series ran 000 through 003 and stopped. Persisted at 3926 nodes and 4554 edges, matching the schema of the four before it after a first attempt got the sprint_id type wrong and omitted two fields. The entry-point anchors carried commit SHAs from two days ago. Stamped to the current tip, explicitly rather than by inference: this list is where a prior host let them go stale for 34 sprints. The ledger records what this session actually did, which was governance rather than product: five framework-class findings drafted as contributions to the .agents nucleus instead of dying in a local index, and one of them corrected because I had diagnosed it wrongly. Ephemeral memory purged after the three surviving heuristics were written to persistent memory — that order matters, and the gate exists to make it deliberate. Submodule verified clean and pinned to the commit the host declares. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Session-close protocol (
close_workflow.md). Documentation and state only; nothing inusers/changed.graph_stats.jsonwas missingThe freshness gate's structural-delta check compares against a tracked snapshot, never
graphify-out/, which is gitignored. Sprint #4 never wrote one, so the series ran 000→003 and stopped:A first attempt used an integer
sprint_idand omittedbuilt_at_commitandcaptured_date. Checked against the schema of the four before it and corrected.Anchors were two days stale
0_SYSTEM_OVERVIEW.mdandGLOBAL_ROADMAP.mdcarried SHAs from before the last three merges. Stamped explicitly rather than by inference — the workflow names this step precisely because a prior host let these anchors go stale for 34 sprints.Memory
Three heuristics were written to persistent memory before the ephemeral purge, which is the order the Heuristic Pulse Gate exists to make deliberate:
Note on RA-12
The rule targets
ai-sprint/[ID]. Sprint #4 was closed and merged two days ago; this session was P5 and P6 work, and all of it landed through reviewed pull requests. There is no live sprint branch, so this goes throughchore/session-close-004— nothing direct tomain, which is what the rule protects.🤖 Generated with Claude Code