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

INTENT.md

@@ -360,49 +360,27 @@ These are logical boundaries first. They do not require separate services or pac
 
 ## Initial Milestones
 
-### M0 — Deterministic Semantic Scenario Runner
+> **Superseded.** This section previously carried its own `M0`–`M3` sequence,
+> which conflicted with two other sequences in the repository. The canonical
+> milestone sequence is now **`docs/TestDriverInitialMilestones.md` (M0–M10)**.
+> Recorded as framework finding `F-0001` (CONCEPT_DRIFT), 2026-08-22.
 
-Implement the conceptual kernel without agentic involvement:
+The former M0–M3 map onto the canonical sequence as follows:
 
-- UseCase,
-- Actor,
-- World,
-- Scenario,
-- SemanticAction,
-- Driver,
-- Observation,
-- Evidence,
-- Oracle,
-- Verdict.
+| Superseded (INTENT.md) | Canonical (`TestDriverInitialMilestones.md`) |
+|---|---|
+| M0 Deterministic Semantic Scenario Runner | M1 Deterministic Semantic Kernel |
+| M1 Agentic Driver | M4 Agentic Realization |
+| M2 Adaptation and Crystallization | M5 Mechanical Adaptation, M6 Defect vs Adaptation, M7 Crystallization |
+| M3 Living Verification | M9 Verification Energy |
 
-Run the Alice/Bob/Carol reference scenario deterministically.
+The canonical sequence additionally introduces M0 (Research Control Plane),
+M2 (Test-Driver Lab), M3 (Self-Verification), M8 (Improvement Loop) and
+M10 (Compression Review), which had no counterpart here.
 
-### M1 — Agentic Driver
-
-Allow an actor agent to realize a semantic action or scenario goal through one interaction surface while maintaining strict actor isolation and evidence capture.
-
-### M2 — Adaptation and Crystallization
-
-Add:
-
-- adaptation classification,
-- learned successful paths,
-- hardening,
-- deterministic test candidate generation,
-- lineage from exploratory discovery to regression test.
-
-### M3 — Living Verification
-
-Add:
-
-- energy,
-- temperature,
-- confidence,
-- retirement,
-- security mutation campaigns,
-- adaptive campaign selection.
-
----
+Execution order is *not* the canonical order — see
+`workplans/TD-WP-0002-vertical-spike-crystallization.md`, which drives one thin
+thread through M1–M7 rather than completing each milestone in turn.
 
 ## Non-Goals for the Initial Project