Repository navigation
D238 — a record known unsound is voided, and nothing is kept from it - #434
Merged
Merged
Conversation
Closes #429. Agent-Session: nstack-os-d238 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
napkinstack-admin
approved these changes
Nov 18, 2026
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.
Closes #429.
Why
On #429's project, two attests shared one build folder for half an hour, so every record made in that window was unsound. A later
nstack atteston the same commit, base and engine kept the module checks of one of those records (D223). The e2e never ran again, and a verifier caught it only by comparing the evidence's date and hash. Nothing could mark a record bad; avoiding the reuse depended on an operator remembering--again.What
Legend: what one void line changes for each reader of the notes.
voids, their times) instead of relying on order. A run with a clock ahead, or one brought in later by a merge of notes, is never brought back._publishable. Its reason is unplaced, like the record's paths.--voidtakes--reason, and neither goes with--again,--body-fileor--labels.07-governance.md§7,INSTALL.mdand the CLI help. Register row D238.Tests
pr-checkreads a voided head as voided until it is attested again.test_attest.pyandtest_pull_request.py: 187 passed.voidslist, withlatestand every reuse reading it._kepton the same commit), now fixed with its own test.🤖 Generated with Claude Code