Record v0.12, and say what the audit work did and did not settle - #32
Merged
Conversation
The tamper-evidence work merged without a roadmap row, so the shipped table stopped at v0.11 while main carried v0.12. Blocker 2 also needed correcting in both places. It read as though nothing had changed since the trail started outliving the node, which undersold the chain and the anchors -- an edit is now detectable, and an attacker who rewrites the chain to be self-consistent is caught by a head recorded where they cannot write. It is still accurate that the blocker stands: both volumes are on the same Docker daemon, so this is tamper evidence and not tamper proofing, and the trail does not leave the machine. Stating both halves is the point; the previous text stated neither. 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
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.
The tamper-evidence work (#31) merged without a roadmap row, so the
shipped table stopped at v0.11 while
maincarried v0.12.What changes
docs/roadmap.mdgains thev0.12rowREADME.mdmoves from "Everything through v0.11" to v0.12Why blocker 2 needed rewording
It still read as though nothing had changed since the trail started
outliving the node. That undersells what landed — an edit is now
detectable, and an attacker who rewrites the chain to be self-consistent
is caught by a head recorded where they cannot write.
It also stays a blocker, and the new text says so in the same breath:
both volumes are on one Docker daemon, so this is tamper evidence and
not tamper proofing, and the trail does not leave the machine.
The previous wording stated neither half. This states both.
Once this is in,
v0.12can be tagged at the merge and the v0.9–v0.12releases cut — there are four tags with no release behind them.
🤖 Generated with Claude Code