From d71b5ca6c1a94415dc3604e9e4145b85168e8dab Mon Sep 17 00:00:00 2001 From: Brummel Date: Tue, 12 May 2026 09:24:24 +0200 Subject: [PATCH] =?UTF-8?q?roadmap:=20brainstorm=20Step=207.5=20=E2=80=94?= =?UTF-8?q?=20re-dispatch=20grounding-check=20on=20any=20post-PASS=20spec?= =?UTF-8?q?=20edit=20(P1=20todo)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/roadmap.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/roadmap.md b/docs/roadmap.md index 5ed9128..a5d17c7 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -77,6 +77,22 @@ context. Pick the next milestone from P1.)_ "AI authoring projection" per Decision 6, programs expressible in one form but not the other are a first-class bug class. +- [ ] **\[todo\]** Brainstorm Step 7.5 — Grounding-check is the *last* + step before the spec is committed. Any post-PASS edit to the spec + (Boss-side polish, user-requested change, anything) must + re-dispatch `ailang-grounding-check` before the commit. Today the + skill's Step 7.5 + Step 8 wording allows a "fix issues inline and + re-run Step 7" loop *without* re-running Step 7.5 — closes the + loop on linguistic self-review only, not on grounding. Update + `skills/brainstorm/SKILL.md`: any change to the spec file after + the grounding-check PASS report invalidates that report and + requires a fresh dispatch before Step 8 commit. + - context: surfaced 2026-05-12 during iter rt.1 planning — Boss + edited the roundtrip-invariant spec to add acceptance #7 + ("tests are pure readers") *after* the PASS report from + `ailang-grounding-check`, then committed the spec without a + re-dispatch. User flagged the skill gap that allowed this. + - [ ] **\[milestone\]** Post-22 Prelude — Show + print rewire — ship `Show` typeclass with `Show Int/Bool/Str/Float` instances; rewire `print` through `Show.show`. Gated on heap-`Str` ABI runtime work