docs(ops): reconcile operations/current.md after two-week gap#934
Merged
Conversation
The active DAG was ~100 PRs and two weeks stale; the entire prior active subgraph (closures 0-2, wave-1/2 items, all ADR-0024 gates) had already shipped. Per the file's own discipline (items leave when they ship): - Collapse the long shipped DAG into a dated Recently shipped ledger grouped by closure with PR refs; git + the PRs remain the record. - Rebuild Active nodes around the one live thread (checkpoint anchoring: #932 -> #872, plus #819 disclosure follow-up). - Refresh Decisions blocked on Otto (#708, idle drafts, #803) and recompute Next farmable. - Note in the update protocol to periodically collapse shipped closures into the ledger.
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
1 participant
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
Refreshes
docs/operations/current.md, which had drifted ~100 PRs and two weeks behind reality (last updated 2026-06-08).Why
The entire prior active subgraph — closures 0–2, wave-1/2 items, and all ADR-0024 verification gates — had already shipped. Per the file's own discipline ("items leave when they ship"):
Active nodesaround the one genuinely-live thread — checkpoint anchoring (refactor(sdk-go): extract portable checkpoint crypto into sdk/go/checkpoint #932 → Checkpoint anchor: production hardening (post-spike follow-ups) #872) plus the Support forensic disclosure (sealing) of tool output, not just parameters (ADR-0012) #819 disclosure follow-up.Decisions blocked on Otto(ci(docs): scheduled doc e2e persona fleet that executes the documented journeys #708, idle drafts Add hermes-agent plugin for Agent Receipts audit trails #532/docs(blog): One Chain, Two Channels, Zero Secrets #442/docs(blog): Native Tool Calls in the Audit Trail #444, Rebrand leftover: data paths, OS user, and env vars still sayagent-receipts#803) and recomputeNext farmable.Docs-only; no code or CI touched.