-## 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. Fifty-four selected positive
+cases pass actual CXTM byte comparisons, including three added by Slice 10. These 54 `:CXTM-EQUAL`
+contracts are PASS. Eight rejection contracts also pass: the five selected Date
+cases and `prefix-undefined`, `prefix-collision`, `prefix-undefined2`.
+One executed leap-second `:CXTM-EQUAL` contract is FAIL due to a documented normative
+baseline discrepancy; 210 imported contracts remain NOT-RUN, including the
+nonzero-offset DateTime original. A green local test run preserves that FAIL,
+rather than changing the upstream baseline. 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, 445 retained CXTM checks, 1,101 Occurrence checks, 150 prefix/datatype checks, 665 integer checks, 715 Decimal checks, 1,806 Date checks, 215 DateTime checks and
+16,294 independent Unicode NFC oracle
+comparisons. The oracle needs Python UCD 15.0 or 15.1 (tables use UCD 15.1.0).
+A report path also produces `<path>.semantics.json` with
+separate model observations, plus `<path>.merging.json`, `<path>.associations.json`
+and `<path>.cxtm.json` (complete actual/expected XML and byte counts),
+plus `<path>.occurrences.json` with separate actual Occurrence objects/properties
+and `<path>.prefixes.json` with all seven selected observations, plus `<path>.integers.json` for integer objects
+and independently checked arithmetic probes, plus `<path>.decimals.json` with
+seven Decimal object observations and 157 independent Decimal arithmetic probes,
+plus `<path>.dates.json` with five original Date results, five original rejections,
+396 independent date/calendar probes and 15 century decisions. `<path>.datetimes.json` records four actual DateTime
+models, 45 independent lexical/canonical probes, two discrepancies and the
+partial unsupported read of the original nonzero-offset case.
+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 10 validation](docs/slice-10-validation.md) for current evidence.
+[Slice 9 validation](docs/slice-9-validation.md) records the accepted Date subset.
+[Slice 8 validation](docs/slice-8-validation.md) records the accepted Decimal subset.
+[Slice 7 validation](docs/slice-7-validation.md) records the accepted Integer subset.
+[Slice 6 validation](docs/slice-6-validation.md) records the preceding accepted subset.
+[Slice 5 validation](docs/slice-5-validation.md) records the preceding accepted subset.
+[Slice 4 validation](docs/slice-4-validation.md) records the accepted baseline.
+[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 10 starts from `2ad41cd1a945a4ce97824464de40646bb899259e` on
+`codex/ctm-slice-10`.
+Slice 9 starts from `195d5f5444d776096b765d04c815c23c3db5f84c` on
+`codex/ctm-slice-9`.
+Slice 8 starts from `17dd58775e25ab495e3c83deb4b5a36f5e5a124b` on
+`codex/ctm-slice-8`.
+Slice 7 starts from `3924d1eac5a070fe5a6a26683e23ac338793f544` on
+`codex/ctm-slice-7`.
+Slice 6 starts from `437ad53ea7539d36db3fa871d0931650b7a6a03e` on
+`codex/ctm-slice-6`.
+Slice 5 starts from `8036a2b1ce009218f33d300edcc5f715ec1d1124` on
+`codex/ctm-slice-5`.
+Slice 4 starts from `35648c4dcc71e8dc6448b64abcacb438e53d64a2` on
+`codex/ctm-slice-4`.
+Slice 3 starts from accepted `66664dbff6275d60dab1bc6a232fa70f7b916b8c` on
+`codex/ctm-slice-3`. Await review before continuing to the next slice.