Skip to content

field note: the fixer is the worst witness - #327

Merged
pdbethke merged 1 commit into
mainfrom
field-note/one-door-at-a-time
Sep 11, 2026
Merged

pdbethke merged 1 commit into
mainfrom
field-note/one-door-at-a-time

Conversation

@pdbethke

Copy link
Copy Markdown
Owner

Seven rounds of cold review on 2026-09-08/09, told as the pattern rather than a findings list — the findings are already in the rc.12/rc.13 changelog, and the pattern is the part that only appears when you read the rounds in order.

The subject: a rule enforced at one door and not the others — and round after round, the thing it caught was my own fix for the previous round.

  • The chain guard added at four doors across three separate rounds, then the comment claiming "every door" reproduced as false in a fifth.
  • Three of my own earlier fixes incomplete in the identical shape (gofmt absence vs. failure; the withheld rate fixed for UNCOVERED and left printing 0.00 for import-only; --push-source honored by the audit rows and not by the event tape).
  • Twice an over-strict fix of mine was worse than the finding it closed, and both were reverted with the finding left standing on the record.
  • A test I wrote that could not fail, caught only by its negative control.
  • A release gate I built that no correct procedure could pass.

Verification. Every specific traces to a file in this repo — RequireIntactChain's doc comment, scripts/check-security.sh, certify_repo_report_selection_test.go, certify_repo_custody_test.go, ledgerdir.go:56, ledgerdir_integrity_test.go:384, sandbox/scrub_token_test.go. Two claims from the first draft that I could not trace to a primary source were cut rather than softened.

It also disambiguates its round numbers against the earlier field note, which counts a different series.

Guard clean, US-spelling grep clean, site builds (82 pages), docs gates pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_011NgkB3eLPBhgfqU1XopR1V

…y own fixes

Seven rounds of cold review on 2026-09-08/09, read in order rather than as a
findings list. The pattern is the subject: a rule enforced at one door and
not the others, including in the fixes I wrote for the previous round.

Every specific traces to a file in this repo:
  - RequireIntactChain's own doc comment records checkpoint (round one),
    append (round three), push and LoadDir (round four), and the "every
    door" wording that was itself reproduced as false (round five, R3).
  - scripts/check-security.sh records the gofmt gate fixed for the tool's
    absence and still passing on its failure.
  - certify_repo_report_selection_test.go records the withheld rate fixed
    for UNCOVERED and left printing 0.00 for the import-only residual.
  - certify_repo_custody_test.go records the event tape shipping audited
    source with no --push-source guard anywhere on the path.
  - ledgerdir.go:56 records the IsLedgerDir narrowing reverted because it
    refused real ledgers; ledgerdir_integrity_test.go:384 records the
    unsigned-entry rule reverted because it refused keyless chains.
  - sandbox/scrub_token_test.go records the vacuous test and its negative
    control.
  - The release gate that made releases impossible is in the changelog.

Claims I could not trace to a primary source were cut rather than softened.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011NgkB3eLPBhgfqU1XopR1V
@pdbethke
pdbethke merged commit fdb70de into main Sep 11, 2026
6 checks passed
@pdbethke
pdbethke deleted the field-note/one-door-at-a-time branch September 11, 2026 15:23
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant