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

Split the jurist read into sendable files; the parent was a contamination hazard

Browse Source 
The steward asked whether to share CONTROL-A-JURIST-READ as pass 1. The honest
answer is no, and the question exposed a defect in how I built it: the parent
file carries BOTH passes plus a 'For the record' section naming exactly what is
withheld — that a defective twin exists and that this is a control in a
measurement. Sending it would have destroyed the read.

An artifact that has to be accompanied by a warning about how to use it is built
wrong. So the parent is now marked DO NOT SEND and is explicitly the steward's
instruction sheet, and two standalone files carry only what is sendable:

  SEND-PASS-1.md  (803 words) — the unanchored read
  SEND-PASS-2.md  (999 words) — the dependency audit, after pass 1 returns

Both are generated from the parent's fenced blocks and leak-checked against a
wordlist: twin, defect, control document, measurement, kernel, Constraint 6,
CONTROL-B, PASS 2, withheld. Both CLEAN. Note the check includes 'PASS 2' — pass
1 must not reveal that a second pass is coming, or the reader may hold back.

Caught by the steward asking a practical question, not by any check of mine. The
leak-check is now mechanical so the next regeneration cannot quietly reintroduce
it.
This commit is contained in:
David F Glidden
2026-08-02 18:46:44 +02:00
parent 7d2a1886e9
commit 33cecdb73a
3 changed files with 189 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/governance/CONTROL-A-JURIST-READ-2026-08-02.md
+11
View File
@@ -1,5 +1,16 @@
# Jurist read request — CONTROL-A, two passes
> ## ⚠ DO NOT SEND THIS FILE
>
> **This file is the steward's instruction sheet.** Its "For the record" section names exactly what is being withheld from the jurist — that a deliberately defective twin exists, and that this document is a control in a measurement. Sending it would destroy the read.
>
> **Send these instead, one at a time, each complete and sendable as-is:**
>
> 1. **`SEND-PASS-1.md`** — send now.
> 2. **`SEND-PASS-2.md`** — send only after PASS 1 has returned.
>
> Both are generated from the fenced blocks below and are checked to contain no reference to the twin, the defects, the kernel, the measurement, or the existence of a second pass. Regenerate them if the blocks below change; do not hand-edit them apart.
**For the steward to relay. Send PASS 1 alone. Do not send PASS 2 until PASS 1 has returned.**
Sending both together destroys the point: PASS 1 is an unanchored read, and PASS 2's framing would anchor it.