David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

memory: supersede the 'verify by eye' clause, and name the case where the remedy is the cause

Browse Source 
The copy-paste-clean note told me to verify a draft parses as intended BY EYE.
Today's instance 6 is the counterexample: two leading spaces before a ## render
as a flawless heading and parse as nothing. By eye is exactly what cannot catch
it. Superseded by exact-string comparison with a negative control.

And the note's own remedy — the fenced block — is what added the indentation. It
stays right for entries and is wrong for whitespace-only repairs, which should go
over as a command that never touches the paste path.

Amendment joined rather than rewritten, so the original stays visible.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T1i5VRfHjD79hfaXjWsBXA
This commit is contained in:
David F Glidden
2026-09-10 19:35:40 +02:00
co-authored by Claude Opus 5
parent 065ff240b1
commit 7ca1540182
2 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/feedback-governance-drafting-copy-paste-clean.md
+14
View File
@@ -15,3 +15,17 @@ When drafting a PENDING/REVIEWED entry for the steward to *place* (the copy-past
**How to apply:** in any `REVIEWED draft (steward copy-paste)` section, emit the block inside a fenced code block (```markdown … ```) so no styling is interpreted, headers are plain `##`, and the steward can select-copy the interior verbatim. Verify the draft parses as intended by eye at the *placed* location's conventions, not the draft doc's.
Authorized at the 2026-07-19 harvest review (steward). Kin: [[feedback-checkable-claim-surfaces-bugs]] (the record's form is part of its correctness).
---
## AMENDMENT — 2026-09-10. The last clause is superseded, and the remedy has a case where it is the cause.
**Joined, not rewritten**, so the original stays visible — the same discipline the register uses for a placed entry.
**⚠ "Verify the draft parses as intended BY EYE" is SUPERSEDED. By eye is precisely what cannot catch the worst case.** REVIEWED-138 was placed with two leading spaces before its `##`. CommonMark permits up to three, so it rendered as a flawless heading and read as correct to everyone who looked at it — while `grep -c "^## REVIEWED-13[89]"` returned **1, not 2**, making the ruling invisible to the wake digest, `governance-drift-check.py`, `governance_item` and every scan of that sitting. **Replace with: verify by exact-string comparison against the draft, with a negative control proving the check can fail.** Over four defects in one day, eye caught none; the check caught all four in minutes.
**⚠ AND THE FENCED BLOCK IS THE CAUSE IN ONE NARROW CASE.** Indentation is exactly what a fenced block in transit adds. For an ordinary entry this is harmless — prose reflows and a heading survives. **For a whitespace-only or line-anchored repair, text-to-paste is the wrong instrument: hand the fix over as a COMMAND the steward runs, which never traverses the paste path at all.** Proven the same day: the fenced replacement introduced the defect; the `sed` one-liner did not.
**The rule, restated whole:** fenced, paste-ready blocks for *entries*; a command for *repairs*; and an exact-string check with a negative control for *both*, in place of the eye.
Evidence: PENDING-181 ADDENDUM 1 and ADDENDUM 2 — six transit corruptions, three distinct mechanisms, of which **only two are catchable by reading at all**.