From 408fef9239820b0764882291f6076b8cdcafeb1c Mon Sep 17 00:00:00 2001 From: Brummel Date: Mon, 11 May 2026 21:32:38 +0200 Subject: [PATCH] =?UTF-8?q?journal:=20gc.1=20=E2=80=94=20append=20cadence-?= =?UTF-8?q?flow=20notes=203+4=20from=20first=20real=20grounding-check=20ru?= =?UTF-8?q?n?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Note 3: agent output format leaked internal-thinking preamble before the structured report block — Iron Law should forbid preamble. Note 4: Boss-requested behaviour change for impending-BLOCK paths — on miss, agent attempts to write missing GREEN test (test code only, never src/) before falling to BLOCK; requires tool + Iron Law update. Both notes are for the future skillsystem-postmortem entry; out of gc.1 scope. --- docs/journals/2026-05-11-iter-gc.1.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/journals/2026-05-11-iter-gc.1.md b/docs/journals/2026-05-11-iter-gc.1.md index 1ee5eaf..9396c24 100644 --- a/docs/journals/2026-05-11-iter-gc.1.md +++ b/docs/journals/2026-05-11-iter-gc.1.md @@ -89,6 +89,26 @@ for gc.1 itself: here so it is not misread, in retrospect, as evidence that the phases are too lenient. +3. **First real run of grounding-check (2026-05-11 same-day, on + the revised Spec-23): PASS, 15 assumptions ratified.** The + agent's output format leaked an internal-thinking preamble + before the structured `GROUNDING-CHECK REPORT` block — the + Iron Law should be tightened to forbid any preamble before the + structured report. Substantively unproblematic (the judgement + and test pins were clear) but a real prompt-discipline gap. + +4. **Behaviour change requested for impending-BLOCK paths.** On a + miss (assumption with no green test), the agent should attempt + to write the missing GREEN test itself — strictly test code, + never `src/`-side app code — and only BLOCK if test creation + fails. This is two changes: (a) tools — add `Write` (or `Edit`) + to the agent frontmatter, today `Read, Glob, Grep, Bash` only; + (b) discipline — Iron Law gains "you may write tests under + `crates/*/tests/` or `#[cfg(test)] mod tests`; you may NOT touch + any file outside test scope." The first real PASS run did not + exercise this path, so the constraint surfaces here as a future + tightening rather than as a tested behaviour. + ## Known debt None.