T01: establish canonical milestone sequence, record F-0001
Three documents defined conflicting milestone sequences; an unqualified reference to e.g. 'M2' was ambiguous across the corpus. - docs/TestDriverInitialMilestones.md (M0-M10) is now canonical - INTENT.md and ConceptModel section 15 carry superseded banners plus a mapping table rather than being deleted - canonical order is explicitly distinguished from execution order - research/findings/ established; F-0001 filed as CONCEPT_DRIFT, resolved via path 2 (concept deliberately revised), with one residual for T10 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 1629012@bnt-lap001 Assistant-Session: 78d4fb13-8a1e-474b-87a3-9b9261c49a39
This commit is contained in:
parent
b21f23cabb
commit
c856cb9e64
6 changed files with 142 additions and 77 deletions
|
|
@ -910,46 +910,21 @@ The conceptual components may initially share a process or codebase. Their separ
|
|||
|
||||
# 15. Initial Development Sequence
|
||||
|
||||
## M0 — Deterministic semantic scenario runner
|
||||
> **Superseded.** This section previously carried its own `M0`–`M3` sequence,
|
||||
> which conflicted with the sequences in `INTENT.md` and
|
||||
> `TestDriverInitialMilestones.md`. The canonical milestone sequence is
|
||||
> **`TestDriverInitialMilestones.md` (M0–M10)**. Recorded as framework finding
|
||||
> `F-0001` (CONCEPT_DRIFT), 2026-08-22.
|
||||
|
||||
Implement:
|
||||
The former M0–M3 corresponded to canonical M1, M4, M5–M7 and M9 respectively.
|
||||
See the mapping table in `INTENT.md` § Initial Milestones.
|
||||
|
||||
- use cases,
|
||||
- actors,
|
||||
- worlds,
|
||||
- semantic actions,
|
||||
- observations,
|
||||
- oracles,
|
||||
- verdicts.
|
||||
|
||||
Execute the reference multi-user scenario without AI.
|
||||
|
||||
## M1 — Agentic driver
|
||||
|
||||
Allow an actor agent to realize a semantic action or use-case subgoal through a browser or API surface while preserving actor isolation and evidence capture.
|
||||
|
||||
## M2 — Adaptation and crystallization
|
||||
|
||||
Implement:
|
||||
|
||||
- adaptation classification,
|
||||
- successful-path persistence,
|
||||
- hardening,
|
||||
- generation of deterministic test candidates.
|
||||
|
||||
## M3 — Living verification
|
||||
|
||||
Introduce:
|
||||
|
||||
- energy,
|
||||
- temperature,
|
||||
- lineage,
|
||||
- retirement,
|
||||
- mutation campaigns,
|
||||
- adaptive test selection.
|
||||
Execution order is *not* the canonical order — see
|
||||
`workplans/TD-WP-0002-vertical-spike-crystallization.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
# 16. Canonical Concept Set v0.1
|
||||
|
||||
The initial test-driver vocabulary is:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue