roadmap: brainstorm Step 7.5 — re-dispatch grounding-check on any post-PASS spec edit (P1 todo)
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user