amadan
AGENTS.md: gates 1 and 2 have their database now
The file said "Gates 1 and 2 need a database and the skeleton has none", which was a status sentence in a binding file — the exact thing the paragraph around it warns against — and this branch made it false. Both gates now exist and run. Also records the part a future reader needs: gate 2's expensive half asserts the sign-in third of its own sentence today, and must be EXTENDED rather than replaced when the directory upsert, the rekey and the roster seed verb land.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 file changed,
+9
−5
AGENTS.md+9 −5
CI passed — run details
diff --git a/AGENTS.md b/AGENTS.md| index 1f09621..2c39dd8 100644 |
| --- a/AGENTS.md |
| +++ b/AGENTS.md |
| @@ -49,11 +49,15 @@ against a seeded corpus of known addresses; a **no-address-at-rest** test |
| asserting the schema has no address column and that a full sign-in plus |
| directory upsert **plus rekey plus the roster seed verb** leaves no readable |
| address anywhere, **WAL |
| -included**; and **no-content-in-logs** (gate 9). **Gates 1 and 2 need a |
| -database and the skeleton has none. Gate 9 needs no database** — it scans |
| -strings, and `cmd/home/main.go` already emits log lines — **so it is not |
| -sequenced behind one**. §13 step 1 lists all three beside the skeleton. A |
| -guard written after the code it guards is a guard written to |
| +included**; and **no-content-in-logs** (gate 9). **Gate 9 needs no database** — it scans strings, and `cmd/home/main.go` |
| +emits log lines — **so it was never sequenced behind one**, and it landed |
| +beside the skeleton. Gates 1 and 2 do need one, and it now exists: gate 1 |
| +scans the raw file, WAL and SHM for canaries, and gate 2 runs in two |
| +halves, a static read of every migration and a full sign-in asserted to |
| +leave no readable address anywhere. Gate 2's expensive half must be |
| +**extended, not replaced**, when the directory upsert, the rekey and the |
| +roster seed verb land — it asserts the sign-in third of its sentence |
| +today. A guard written after the code it guards is a guard written to |
| pass. (Stated as the rule rather than as a status: which gates exist today |
| is a question for `git log`, and a status line in a binding file is a |
| sentence that goes stale without anyone noticing.) |