-## Recorded result and authority
-
-The pinned corpus has 231 valid CTM inputs, 42 invalid inputs, 231 CXTM baselines
-and 22 auxiliary files in its CTM subtree, with no unmatched/missing baseline.
-All 273 imported CTM cases are **NOT-RUN**; none passes a nonexistent reader.
-Infrastructure fixtures exercise PASS, FAIL, UNSUPPORTED and NOT-RUN separately.
-
-The upstream CTM suite targets the **draft dated 2010-03-31**. Passing that suite
-alone would not establish full ISO/IEC 13250-6:2010 conformity. Published ISO
-standards are normative; this corpus and Ontopia are independent evidence.
-
-See [inventory and provenance](docs/inventory.md),
-[coverage and the first five proposed Slice 1 cases](docs/coverage.md),
-[architecture and Document-IRI policy](docs/architecture.md), and
-[execution evidence](docs/validation.md).
-The [machine-readable report](reports/validation.json) records actual imported
-case contracts and the passing infrastructure check names, without claiming
-CTM implementation. Nothing from Slice 1 is automatically started.
+## Current validation and historical foundation
+
+The complete pinned corpus remains unchanged: 231 valid CTM inputs, 42 invalid
+inputs, 231 CXTM baselines and 22 CTM auxiliary files. Twenty-four selected semantic
+cases pass; their imported canonical contracts remain NOT-RUN. Only
+`ctm/invalid/prefix-undefined.ctm` is PASS under its CTM rejection contract;
+272 imported contracts remain NOT-RUN. Unsupported constructs and I/O errors
+cannot count as that required rejection.
+
+The full launcher runs the retained 54 foundation checks, two Python integrity
+fixtures, 123 retained identity checks, 646 merge checks, 657 Association checks,
+imported-report validation and selected baseline
+property evidence. A report path also produces `<path>.semantics.json` with
+separate model observations, plus `<path>.merging.json` and `<path>.associations.json`.
+The merge checks include 128 graph/order variants with an independent reachability
+oracle. Reports are deterministic across the tested SBCL versions and checkout
+relocation. See [Slice 3 validation](docs/slice-3-validation.md),
+[imported contracts](reports/slice-1/validation.json) and
+[semantic observations](reports/slice-1/semantics.json).
+
+[Slice 0 inventory](docs/inventory.md), [architecture](docs/architecture.md),
+[coverage](docs/coverage.md) and [validation](docs/validation.md) remain historical
+foundation records. Their original report/logs are preserved. Their statements
+about absent reader/model systems describe Slice 0, not the current branch.
+Slice 1 is built from `9c83db34eb1ba8091b004433f088056717dbaa7e` on
+`codex/ctm-slice-1`. Slice 2 starts from the accepted Slice 1a commit
+`fb60afd548d679d83fd8ec76bc5ff384c1e23e5f` on `codex/ctm-slice-2`.
+Slice 3 starts from accepted `66664dbff6275d60dab1bc6a232fa70f7b916b8c` on
+`codex/ctm-slice-3`. Await review before continuing to the next slice.