Repository navigation
Tags
Tags
docs: post-tag reconciliation
Catch the canonical brief up to where the code actually is after the
R2 tag. None of these are scope changes; they're stale references
that survived the release.
- ACCEPTANCE.md
- R2 functional / implicit criteria flip from `⋯` to `✓`. Two new
`✓` rows for the surfaces the original R2 list didn't enumerate
(Forensic replay, Phylogeny view, New-visitor tour) since those
landed within R2 even though they weren't pre-listed.
- "Deferred to a later release" loses Forensic replay (it
shipped); R5 patch-incompatibility stays.
- R0 verdict acknowledges that the deferrals (extra mutation
kinds, state-rewind scrub) have since landed in R1 and R2.
- R0 functional row for Forensic replay flips from `—` deferred
to `✓` (with note that the affordance came in with R2).
- ARCHITECTURE.md "Message families"
- Command list adds `revokeDecree`, `releaseQuarantine`,
`rewindToTick`.
- Domain-event list adds `patchApplied`, `decreeQueued`,
`decreeFired`, `decreeRevoked`, `quarantineImposed`,
`quarantineLifted`.
- Query list adds `substrate`, `decreeQueue`, `listSaves`.
- PROCESS.md Layer 2 paragraph
- Drops the "skill is to be authored when R0 implementation
begins" line; the skill exists at `.claude/skills/bobivolve-review/`
and has been in use throughout R1 and R2.
- TODO.md
- Drops the pause-button-flicker entry; the heartbeat-driven
`paused` reconciliation that caused it was removed in commit
610d972 (`ui/store: drop heartbeat-driven 'paused'
reconciliation`).
CLAUDE.md: codify the three load-bearing feedback patterns Auto-memory at ~/.claude/projects/-Users-jonathan-hitchcock-src-bobivolve/memory/ is local-only — a laptop death loses it, and a fresh checkout on a new machine starts blank. Three of those memories are project-load-bearing (release tags need sign-off; modal-on-action over perpetual UI; hide irrelevant items over compressing relevant ones); they now live here in git so they survive. Auto-memory keeps its job for discovering new patterns, but the established three are redundant in the repo rather than a single point of failure.
Ship R0 — Petri Dish Living docs reconciled to reality: every R0 feature flipped to ✓ in FEATURES.md; ACCEPTANCE.md verdict moves from "pending sign-off" to "shipped" with the two carry-overs marked deferred and rationale on file (extra mutation kinds gated on R1's richer firmware; state-rewind scrub gated on later releases producing more events worth scrubbing to). README status updated to name the release. TODO entries for the deferred items retagged from #r0 to #r1.