Planning v3.9: record M11's long-run evidence, and correct what v3.7 claimed
The planning package still described M01 as outstanding. It now records the evidence run on96c1bf5and the two product defects found on the way. It also corrects three statements that were never true. - V1-ACCEPTANCE-TESTS.md: result blocks for M01-M04. M04 is recorded as recovered through authoritative state, with the owner's acceptance of that on 2026-09-13 and the positional precondition explained. Correction: v3.7 said this file carried M11 results against every REQUIRED test. None were written, and the per-test matrix is the M11 report's §F. The §P3 M11 disposition said the report records the identity diagnostic's findings. It does not, and the disposition now says so. - BUILD-MILESTONES.md: the M11 status block records the long-run evidence, the write-lock and protocol-leak defects, and what is left for the reviewer. - DATA-MODEL.md §28B: M11 added two columns, not one. settings.context_window_override (migration 94,ef25b0a) was never recorded. - TECHNICAL-DESIGN.md: "Background failure observability" gains the rule that nothing in a turn writes before the model call, and new §15.4 records that stored narration carries story only, with the extractor's rules. - CONTEXT-AND-MEMORY.md §51 and ADR 013: as-implemented notes for the same two fixes. - README.md and VERSION.md: status, milestone map, stop rule, and the v3.9 entry. - M11 report §Q: the "not revised" note is replaced by what v3.9 revised. No requirement changes. No code changes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136VBTMUKWYeU6G9HgbDbND
This commit is contained in:
co-authored by
Claude Opus 5
parent
d1988065e5
commit
3652dc6fae
@@ -1508,9 +1508,12 @@ accepted for v1, or a decision for the owner at acceptance.
|
||||
| `planning/reports/M11-IMPLEMENTATION-REPORT.md` | **Revised 2026-09-14**: M01-M04 on the complete evidence run; §A, §B, §C, §E.1, §F, §G, §J, §K, §N, §O, §P and §R rewritten; the §G.0 addendum removed. | milestone report |
|
||||
| `DEVELOPMENT.md` | The pointer to the removed §G.0 replaced; a new section on logging a GPU inference host during a long run. | developer docs |
|
||||
|
||||
**Not revised with this report:** `planning/V1-ACCEPTANCE-TESTS.md`,
|
||||
`planning/BUILD-MILESTONES.md`, `planning/VERSION.md` and `planning/README.md`
|
||||
still carry what the first revision and `ef25b0a` wrote into them.
|
||||
**Revised after this report, in planning package v3.9 (2026-09-14):**
|
||||
`planning/V1-ACCEPTANCE-TESTS.md` gained result blocks for M01-M04 and corrected
|
||||
its M11 disposition. `planning/BUILD-MILESTONES.md`, `planning/VERSION.md` and
|
||||
`planning/README.md` record the long-run evidence. `DATA-MODEL.md` §28B now
|
||||
records migration 94, and `TECHNICAL-DESIGN.md` (new §15.4), `CONTEXT-AND-MEMORY.md`
|
||||
§51 and ADR 013 record the two defect fixes as implemented.
|
||||
|
||||
**Implementation facts added:** §15.2, §28B, §8A's implementation note, §42B, and
|
||||
the M11 status block. Each records what the code does; none changes what is
|
||||
|
||||
Reference in New Issue
Block a user