astp-docs-server 0.1.0__py3-none-any.whl

astp_docs_server/corpus/open/CONFORMANCE-CONTEXT.md

@@ -0,0 +1,332 @@
+# ASTP — Context-Commitment Conformance Test Vectors
+
+**Version:** 1.0.0
+**Status:** Stable — ratified with SPEC 6.0.0 in Episode of Record `80e5a2dd-3d9f-45d0-abfb-6489c8caf1b8` ([`docs/RATIFICATION-6.0.0.md`](./docs/RATIFICATION-6.0.0.md)); the values were generated while 6.0.0 was a draft and none changed at ratification
+**Authors:** Scorched Earth Labs
+**Date:** 2026-09-22
+**Applies To:** SPEC.md 6.0.0 — §4.8 ContextEntryNode, §4.9 Erasure and ErasureTombstone, §5.7 Episode Root version 3, §5.7.3 Context Manifest, §5.8 `spine_algorithm_version` 3, §9.2–§9.3 as extended, G-41, G-42, G-43.
+**Companions:** [CONFORMANCE-REPRODUCIBILITY.md](CONFORMANCE-REPRODUCIBILITY.md) (§5.6–§5.8, `spine_algorithm_version` 0–2), [CONFORMANCE-TRUST.md](CONFORMANCE-TRUST.md) (§16), [CONFORMANCE-LAYER3.md](CONFORMANCE-LAYER3.md) (§21).
+
+---
+
+## 1. Overview
+
+These vectors test the one thing 6.0.0 adds — a sealed commitment to what an Episode's agents were *given* — and the one thing it states: **the seal proves history, not retention.** Every expected value below is pinned in [`vectors/6.0.0/context-commitment.json`](./vectors/6.0.0/context-commitment.json), generated by `vectors/6.0.0/generate.py` and never edited by hand, and is reproduced twice in `tests/conformance/test_context_commitment_v1_vectors.py`: once by the reference package and once by a `hashlib`-only implementation written from the SPEC text that imports nothing from `astp`.
+
+The Episode is the one the ratified 5.0.0 vectors seal (`550e8400-e29b-41d4-a716-446655440000`, its seven Segments, five Signals and seven structural members), so the version 2 roots here are the ratified values byte for byte. A conforming implementation MUST pass all vectors marked **REQUIRED**. Format follows [CONFORMANCE-TRUST.md §1](CONFORMANCE-TRUST.md); hash values are lowercase hex and enter every construction as 32 raw bytes under the §5.1.1 field encoding.
+
+Reference implementation: `astp/core/context_v1.py`; `astp.core.seal_v2.reproduce_episode_root` dispatches version 3.
+
+**The shared inputs.** Seven context entries on the base Episode, provided at one-minute intervals from `2026-01-01T00:01:00.123Z`; identifiers are fixed for reproducibility and MUST be random in practice (§5.2). The salt is fixed for the same reason and MUST be 32 CSPRNG bytes in practice (§5.3).
+
+| # | `entry_id` | `entry_type` | `capture_state` | `salted` | `verifiability_at_seal` | `entry_hash` |
+|---|---|---|---|---|---|---|
+| 1 | `…0200` | attachment | captured | false | verifiable | `b08d864e0d6d41321cecbd90483ee1396ece80368f72ca496f772dfd04f85663` |
+| 2 | `…0201` | retrieval | captured | false | attested | `a4dabb6716c72fc11c6e2a3cc2569c67c807c7b4c2aa882fb0dfb7ac4ef3f885` |
+| 3 | `…0202` | retrieval (low-entropy personal data) | captured | **true** | verifiable | `4f45678a1893131e24d4afddd1350fbfcc7ce3f7cb5fe4ec893c76e58ff92704` |
+| 4 | `…0203` | external | captured | false | verifiable | `e88d185230ffbe206d333f59f4156fb7337b5ced90083e9b704727c73dea0397` |
+| 5 | `…0204` | tool_output | captured | false | verifiable | `956432ad9964673fced63541a9e1e6c3bf864ac5452a3d9f393bf60c6b8a5572` |
+| 6 | `…0205` | retrieval | **declared_incomplete** | false | — | `0dbaaff8a22a5d772c49350bb94fc6fa825a635660fb128c2420bdff070d4cc3` |
+| 7 | `…0206` | retrieval, `resolves` #6 | captured | false | verifiable | `eb174452baa2d2eb6ba47329dec7af36150cc07c669cd3fc92c5cb696102a643` |
+
+Full field values are in the vector file's `entries` list. The base Episode's version 2 components: `spine_root` `4420e38a22409317822ac14e3d5bc8069e6556c0fc08928290f76d23396daa01`, `signal_manifest_hash` `70dbc8e8f2e87b63e49187979b14ad56ba11219b42be132015c23dcad36acb43`, `structural_manifest_hash` `0a4b777227b87ee0d6c8efd5b2e9a5fc05c02e61d677f2460f868ab06779b537`, `exclusion_hash` `ddea405cc1729ebf63d93b16d723873ad02f9f64af3cc159bf86e5f999b02ce1`, `episode_root_hash` (version 2) `f0511b4d1be172554b9f87ec64d400d24a1409f1742ad72f628bf5ab7b7d33f0`.
+
+---
+
+## 2. Content Commitment (§4.8.3)
+
+**CC-001** — Plain Content Commitment
+- **Class:** REQUIRED
+- **Spec Reference:** §4.8.3
+- **Description:** `CONTEXT_CONTENT:v1:` over the bytes as provided, under the BYTES field encoding (tag `01`, u32 length, bytes).
+- **Inputs:**
+  ```
+  content (hex): 255044462d312e370a312030206f626a203c3c202f54797065202f436174616c6f67203e3e20656e646f626a0a2525454f460a
+  construction:  SHA3-256("CONTEXT_CONTENT:v1:" ‖ BYTES(content))
+  ```
+- **Expected Output:**
+  ```
+  content_hash: 9fbce78d71635571ef48ac04c99f1f340ac5141749f62bde5a77b425192d0baf
+  ```
+- **Failure Condition:** Any other value; a hash over the hex text of the content or over an extraction of it.
+
+**CC-002** — Salted Content Commitment
+- **Class:** REQUIRED
+- **Spec Reference:** §4.8.3, G-42
+- **Description:** `CONTEXT_CONTENT_SALTED:v1:` over the 32-byte salt and then the bytes; the salt is a separate BYTES field, so the boundary between salt and content cannot be moved.
+- **Inputs:**
+  ```
+  content (utf-8): 1979-03-14
+  salt (hex):      000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
+  construction:    SHA3-256("CONTEXT_CONTENT_SALTED:v1:" ‖ BYTES(salt) ‖ BYTES(content))
+  ```
+- **Expected Output:**
+  ```
+  content_hash (salted): f94cc9f2c956d78e7a1c9c17ac6ae74580da6a8cb8256d923f012afa8b0e501a
+  content_hash (plain, for contrast — what G-42 forbids for this content): 4ae9d00037107b8d1ed647f47bf2e4c97311929b4c5d6dd2a57b678fffb5c772
+  ```
+- **Failure Condition:** Any other value; a salt of any length but 32 accepted; the plain construction used for content classified low-entropy personal data.
+
+---
+
+## 3. Entry Hash (§5.7.3)
+
+**CM-002** — Entry Hash Binds Its Claims and Nothing Else
+- **Class:** REQUIRED
+- **Spec Reference:** §5.7.3, §4.8.6
+- **Description:** the preimage is the thirteen fields in the stated order; `source_ref`, `content_ref`, `salt_ref`, `erasure_state` and any implementation classification are outside it. Changing any preimage field changes the hash; changing any side-channel field does not.
+- **Inputs:**
+  ```
+  preimage: entry_id UUID ‖ episode_id UUID ‖ entry_type STRING ‖ provided_to STRING ‖ provided_at TIMESTAMP ‖ provided_before_sequence_index UINT|NULL ‖ capture_state STRING ‖ content_hash HASH|NULL ‖ salted BOOL ‖ verifiability_at_seal STRING|NULL ‖ media_type STRING|NULL ‖ source_version_hash HASH|NULL ‖ resolves_entry_hash HASH|NULL
+  entry #1 (attachment): see vectors "entries"[0]
+  ```
+- **Expected Output:**
+  ```
+  entry_hash: b08d864e0d6d41321cecbd90483ee1396ece80368f72ca496f772dfd04f85663
+  unchanged when source_ref, content_ref, salt_ref, erasure_state change
+  changed when any preimage field changes (each tested)
+  ```
+- **Failure Condition:** A side-channel field moving the hash (erasure would then move a sealed preimage); a preimage field not moving it.
+
+**CM-002a** — Declared-Incomplete Entry
+- **Class:** REQUIRED
+- **Spec Reference:** §4.8.5, §5.7.3
+- **Description:** NULL `content_hash`, `salted` false, NULL `verifiability_at_seal`, encoded as NULL fields (`00`); a captured entry MUST carry a content hash and a verifiability state.
+- **Inputs:**
+  ```
+  entry #6: capture_state=declared_incomplete, content_hash=NULL, salted=false, verifiability_at_seal=NULL, media_type=NULL
+  ```
+- **Expected Output:**
+  ```
+  entry_hash: 0dbaaff8a22a5d772c49350bb94fc6fa825a635660fb128c2420bdff070d4cc3
+  ```
+- **Failure Condition:** A declared-incomplete entry accepted with content, or a captured entry accepted without verifiability.
+
+---
+
+## 4. Context Manifest (§5.7.3)
+
+**CM-003** — Manifest Is Order-Independent; Removal and Posture Change It
+- **Class:** REQUIRED
+- **Spec Reference:** §5.7.3
+- **Description:** the tree is the §5.4 version 2 tree over entry hashes sorted ascending bytewise; the manifest hash binds the posture and the count with the tree root.
+- **Inputs:**
+  ```
+  entry hashes: the seven above, in any insertion order
+  capture_posture: declared_only
+  construction: SHA3-256("CONTEXT_MANIFEST:v1:" ‖ STRING(posture) ‖ UINT(n) ‖ HASH|NULL(context_tree_root))
+  ```
+- **Expected Output:**
+  ```
+  context_tree_root (sorted leaves): e730a2153f39eb61b27888528000ffdc0b88a94a24f3daf29300126a9d42acc1
+  sorted leaf order (entry_id suffixes): 0205, 0202, 0204, 0201, 0200, 0203, 0206
+  context_manifest_hash (declared_only, 7):        94e7681209cb0315427622aee9b22abf832e5e35ba653cf7e692faa413e75df7
+  same entries, reverse insertion order:            94e7681209cb0315427622aee9b22abf832e5e35ba653cf7e692faa413e75df7
+  without entry #2:                                 54a733a5c6592d150f5374cb1327a44a72e2fd45a67ca20d07bda2a4cb4d5004
+  posture all_external instead:                     68c1bc568cd1b4967dc8214a450dbb2e8a185841cddd76c5472451dfa70dcf92
+  ```
+- **Failure Condition:** Insertion order changing the hash; a removed entry or a changed posture leaving it unchanged.
+
+**CM-001** — Empty Manifest Is Defined
+- **Class:** REQUIRED
+- **Spec Reference:** §5.7.3, §5.7
+- **Description:** an Episode with zero context entries composes `n = 0` and a NULL root, seals under version 3 and reproduces from stored state.
+- **Inputs:**
+  ```
+  entries: none
+  capture_posture: none
+  ```
+- **Expected Output:**
+  ```
+  context_manifest_hash (none, 0):          66be9e2d4febffe1afb2afb2e388aec945777f4f8b1ef58c1a5a234ea9eedb5d
+  context_manifest_hash (declared_only, 0): 0bcf1339549cd0673d1776d198b856dba92987798b0ba9c9838ee1a936076e7d
+  episode_root_hash (version 3, posture none): 490fb1f566a5ef75640f54d6d5550bd7706073809902d18348a870f188fd6882
+  ```
+- **Failure Condition:** A version 3 seal refused for an Episode without entries; a tree root computed for zero leaves; the two postures giving one hash.
+
+---
+
+## 5. Episode Root Version 3 (§5.7, §5.8)
+
+**ER3-001** — Six-Field Root Selected by `spine_algorithm_version` 3
+- **Class:** REQUIRED
+- **Spec Reference:** §5.7, §5.8
+- **Description:** the version 2 root's five fields unchanged, then `context_manifest_hash`; the spine root is byte-identical to version 2.
+- **Inputs:**
+  ```
+  episode_id:               550e8400-e29b-41d4-a716-446655440000
+  spine_root:               4420e38a22409317822ac14e3d5bc8069e6556c0fc08928290f76d23396daa01
+  signal_manifest_hash:     70dbc8e8f2e87b63e49187979b14ad56ba11219b42be132015c23dcad36acb43
+  structural_manifest_hash: 0a4b777227b87ee0d6c8efd5b2e9a5fc05c02e61d677f2460f868ab06779b537
+  exclusion_hash:           ddea405cc1729ebf63d93b16d723873ad02f9f64af3cc159bf86e5f999b02ce1
+  context_manifest_hash:    94e7681209cb0315427622aee9b22abf832e5e35ba653cf7e692faa413e75df7
+  construction: SHA3-256("EPISODE_ROOT:v3:" ‖ UUID ‖ HASH ‖ HASH ‖ HASH ‖ HASH ‖ HASH)
+  ```
+- **Expected Output:**
+  ```
+  episode_root_hash: 22675041b1af6243fe8c72f318ca853a6e775073355c718116c9ac0d19fe0e88
+  seal record identifiers: spine_algorithm_version 3, ordering_version 2, hash_version 2
+  ```
+- **Failure Condition:** Any other value; a separate root-version identifier on the record (§5.8: one identifier selects the whole construction).
+
+**CM-010** — A Version 2 Seal Is Unchanged by Context Entries
+- **Class:** REQUIRED
+- **Spec Reference:** §5.7, §5.8
+- **Description:** context entries are members of no version 2 root; the same Episode, holding the seven entries, seals under version 2 to the ratified 5.0.0 value.
+- **Inputs:**
+  ```
+  the base Episode with the seven entries present
+  spine_algorithm_version: 2
+  ```
+- **Expected Output:**
+  ```
+  episode_root_hash (version 2): f0511b4d1be172554b9f87ec64d400d24a1409f1742ad72f628bf5ab7b7d33f0   (= vectors/5.0.0 episode_root_v2.hash)
+  episode_root_hash (version 3): 22675041b1af6243fe8c72f318ca853a6e775073355c718116c9ac0d19fe0e88   (differs)
+  ```
+- **Failure Condition:** A version 2 root that changes when entries exist; a version 3 root equal to the version 2 root.
+
+---
+
+## 6. Inclusion Proofs (§9.2)
+
+**CM-004** — One Entry Proven Without the Others
+- **Class:** REQUIRED
+- **Spec Reference:** §9.2, §5.7.3
+- **Description:** the §9.2 proof over the context tree; `leaf_index` is the entry's position in the sorted leaf list; the verifier reproduces the tree root, then the manifest hash from posture and count, then the Episode root.
+- **Inputs:**
+  ```
+  entry: #3 (entry_hash 4f45678a1893131e24d4afddd1350fbfcc7ce3f7cb5fe4ec893c76e58ff92704)
+  leaf_index: 1   leaf_count: 7
+  siblings: ["5c2e34164e93e1de4d62b5b498cb1c6cfb5e456627f26cae21e1ad0140228ae9", "f6d2ee6739f138deff2724d247ae8ceb5e70b112f1b74bbd5d929af5cff06429", "d5c030cda42f4363eac47a200e2055334f4507f42de83ca1fb3b1373c6cc2f08"]
+  capture_posture: declared_only   entry_count: 7
+  ```
+- **Expected Output:**
+  ```
+  context_tree_root:     e730a2153f39eb61b27888528000ffdc0b88a94a24f3daf29300126a9d42acc1
+  context_manifest_hash: 94e7681209cb0315427622aee9b22abf832e5e35ba653cf7e692faa413e75df7
+  episode_root_hash:     22675041b1af6243fe8c72f318ca853a6e775073355c718116c9ac0d19fe0e88
+  ```
+- **Failure Condition:** The proof verifying at any other leaf_index, under any other posture, or for any other count.
+
+---
+
+## 7. Append-Only Repair (§4.8.5)
+
+**CM-005** — A Resolving Entry Binds the Resolved Entry's Hash
+- **Class:** REQUIRED
+- **Spec Reference:** §4.8.5, §5.7.3
+- **Description:** entry #7 carries `resolves` = entry #6; its preimage's last field is #6's entry hash; #6 is unchanged.
+- **Inputs:**
+  ```
+  resolved (declared_incomplete) entry_id: …0205
+  resolving entry_id: …0206, resolves = …0205
+  ```
+- **Expected Output:**
+  ```
+  resolved entry_hash:  0dbaaff8a22a5d772c49350bb94fc6fa825a635660fb128c2420bdff070d4cc3
+  resolving entry_hash: eb174452baa2d2eb6ba47329dec7af36150cc07c669cd3fc92c5cb696102a643
+  ```
+- **Failure Condition:** The resolving entry's hash unchanged when the resolved entry's hash changes; a `resolves` naming an entry outside the Episode, a captured entry, or an entry that itself resolves.
+
+---
+
+## 8. Erasure (§4.9; G-43)
+
+**CM-006** — Erasure Is Content-Plane and Witnessed
+- **Class:** REQUIRED
+- **Spec Reference:** §4.9.2, §4.9.3, G-43
+- **Description:** after erasure of entry #3: `content_ref` and `salt_ref` NULL, `erasure_state` tombstoned; the entry hash, the manifest hash and the Episode root are unchanged; a codicil tombstone binds the entry's unchanged hash.
+- **Inputs:**
+  ```
+  entry #3 before: content_ref=blob://ctx/e3, salt_ref=salt://ctx/e3, erasure_state=present
+  tombstone: tombstone_id …0400, entry_id …0202, erased_at 2026-01-01T01:00:00.123000Z, erasure_authority GDPR-Art17, erasure_request_id dsr-2026-0142, erased_by privacy-officer
+  construction: SHA3-256("ERASURE_TOMBSTONE:v1:" ‖ UUID ‖ UUID ‖ UUID ‖ HASH(entry_hash) ‖ TIMESTAMP ‖ STRING ‖ STRING ‖ STRING)
+  ```
+- **Expected Output:**
+  ```
+  entry #3 after: content_ref=NULL, salt_ref=NULL, erasure_state=tombstoned
+  entry_hash (unchanged):            4f45678a1893131e24d4afddd1350fbfcc7ce3f7cb5fe4ec893c76e58ff92704
+  tombstone_hash:                    05dac249ff0fcbd8f9022f3e57e173821541b20f0b2af54d1f65d168276ef384
+  context_manifest_hash (unchanged): 94e7681209cb0315427622aee9b22abf832e5e35ba653cf7e692faa413e75df7
+  episode_root_hash (unchanged):     22675041b1af6243fe8c72f318ca853a6e775073355c718116c9ac0d19fe0e88
+  ```
+- **Failure Condition:** Any sealed value moving; an erased entry reported as an integrity failure; a tombstone outside the codicil chain; content destroyed without the salt or the reverse.
+
+**CM-007** — A Salted Commitment Confirms No Guess Once the Salt Is Gone
+- **Class:** REQUIRED
+- **Spec Reference:** §4.8.3, G-42
+- **Description:** stated as a property, tested by construction: the plain commitment to `1979-03-14` equals a recomputation from the guess; the salted one does not, under no salt and under any wrong salt, across the whole low-entropy space.
+- **Inputs:**
+  ```
+  guess: 1979-03-14 (and every 1979-03-DD)
+  plain content_hash:  4ae9d00037107b8d1ed647f47bf2e4c97311929b4c5d6dd2a57b678fffb5c772
+  salted content_hash: f94cc9f2c956d78e7a1c9c17ac6ae74580da6a8cb8256d923f012afa8b0e501a
+  ```
+- **Expected Output:**
+  ```
+  SHA3-256("CONTEXT_CONTENT:v1:" ‖ BYTES(guess)) == plain content_hash            (a plain commitment is an oracle)
+  SHA3-256("CONTEXT_CONTENT:v1:" ‖ BYTES(guess)) != salted content_hash
+  SHA3-256("CONTEXT_CONTENT_SALTED:v1:" ‖ BYTES(any wrong salt) ‖ BYTES(guess)) != salted content_hash
+  only the true salt reproduces it — verification of an un-erased salted entry needs that one entry's salt (§4.9.5)
+  ```
+- **Failure Condition:** A salted commitment reproducible without its salt.
+
+---
+
+## 9. External Entries (§4.8.4)
+
+**CM-008** — An External Entry Verifies Without a Fetch
+- **Class:** REQUIRED
+- **Spec Reference:** §4.8.4, §4.8.6
+- **Description:** the URI and fetch metadata in `source_ref` are provenance outside the preimage; `source_version_hash` is NULL; a verifier MUST NOT re-fetch and treat a difference as a failure.
+- **Inputs:**
+  ```
+  entry #4: entry_type=external, source_ref='https://rates.example/sheet?date=2026-01-01 status=200 etag="7f3a"', source_version_hash=NULL
+  source_ref changed to: 'https://rates.example/sheet?date=2026-01-02 status=404'
+  ```
+- **Expected Output:**
+  ```
+  entry_hash before: e88d185230ffbe206d333f59f4156fb7337b5ced90083e9b704727c73dea0397
+  entry_hash after:  e88d185230ffbe206d333f59f4156fb7337b5ced90083e9b704727c73dea0397   (unchanged)
+  ```
+- **Failure Condition:** The entry hash depending on the URI or on the result of a fetch.
+
+---
+
+## 10. Governance at the Seal (G-41, G-42)
+
+**CM-009** — Safe Only Together
+- **Class:** REQUIRED
+- **Spec Reference:** G-42, CM-009
+- **Description:** an implementation that claims 6.0.0 context commitment and does not implement G-42 is non-conformant. In the reference package the rule is enforced where the seal happens: an entry the implementation classified as low-entropy personal data and committed plain is refused.
+- **Inputs:**
+  ```
+  entry #3 with salted=false and the plain content_hash 4ae9d00037107b8d1ed647f47bf2e4c97311929b4c5d6dd2a57b678fffb5c772, classified low_entropy_personal
+  ```
+- **Expected Output:**
+  ```
+  seal refused (G-42 violation)
+  the same entry with no classification seals — the classifier's quality is the implementation's residual risk (§4.9.5)
+  ```
+- **Failure Condition:** A ConformanceDeclaration claiming 6.0.0 context commitment from an implementation that commits low-entropy personal data plain.
+
+**G41-001** — Posture Required; an Undeclared Gap Blocks the Seal
+- **Class:** REQUIRED
+- **Spec Reference:** G-41, §5.7.3, §4.8.5
+- **Description:** a version 3 seal without a `capture_posture` is refused; an entry whose write did not complete as `captured` or `declared_incomplete` blocks the seal.
+- **Inputs:**
+  ```
+  seal with capture_posture = NULL
+  seal over an entry with capture_state = pending
+  ```
+- **Expected Output:**
+  ```
+  both refused (G-41 violation)
+  ```
+- **Failure Condition:** A version 3 seal without a posture; a seal over an entry in a non-terminal capture state.
+
+---
+
+## 11. Retained Constructions
+
+Nothing here changes a value sealed under `spine_algorithm_version` 0, 1 or 2. RP-001 … RP-011 of [CONFORMANCE-REPRODUCIBILITY.md](CONFORMANCE-REPRODUCIBILITY.md) continue to apply unchanged, and CM-010 above is the statement of that for version 2 seals of Episodes that hold context entries.

astp_docs_server/corpus/open/CONFORMANCE-CROSS-EPISODE-LINKING.md

@@ -0,0 +1,258 @@
+# ASTP — Cross-Episode Linking & Grouping Conformance Test Vectors
+
+**Version:** 1.1.0
+**Status:** Stable
+**Authors:** Scorched Earth Labs
+**Date:** 2026-09-19
+**Applies To:** SPEC.md §20 (Cross-Episode Linking & Grouping), 5.1.0 (SPEC §20 as of 5.1.0; see the note in §1)
+
+---
+
+## 1. Overview
+
+> **SPEC 5.0.0 / 5.1.0 note.** SPEC §20 →2 now defines `EpisodeLink.content_hash` as `EPISODE_LINK:v2:` — binding each end's Episode root when that end was sealed at link creation, the type, exact strength, every inference signal (`LINK_SIGNAL:v2:`) in order and the threshold, with health, quarantine and `created_by` **out** of the preimage (they are lifecycle and provenance, the audit chain's). The 4.x preimage this document describes, which bound `health_state` and the quarantine fields and so changed whenever a link's health did, is retained in SPEC only as the definition of links already written; the `LINK_INTEGRITY` field snapshot is the bound set. The reference writer (`write_episode_link_sync`) fills `source_episode_root` / `target_episode_root` from the graph and stamps the 5.0.0 form from `astp` 0.5.0; links written before that carry the 4.x form this document describes (`compute_episode_link_content_hash_4x`). `MembershipRecord` and `ConformanceDeclaration` hashes are unchanged. The audit records these operations write are the version 2 audit record of SPEC §8 (`GENESIS` → NULL); `GroupingSystem` reserves only the protocol's own value — `astp_native` from astp 0.6.0, with `ariadne_native` retained as the value carried by records written before it (`group_system` is in the MembershipRecord preimage).
+
+This document specifies the conformance test vectors for the **Cross-Episode Linking & Grouping** feature family of ASTP (the AI State Tree Protocol; SPEC §20). A conforming implementation MUST pass all vectors marked **REQUIRED**. Vectors marked **RECOMMENDED** test behaviors that conforming implementations SHOULD support.
+
+These are **cross-implementation-consistency** vectors, not hardcoded golden-hash values. A hash vector specifies the canonical byte layout (ordered field set + canonicalization rules) and asserts that **two conforming implementations MUST produce identical bytes for the same input tuple**. This is wire-tier conformance (§20 →12.1): the protocol fixes the preimage, not a specific digest. Where a vector references SPEC §20, it uses the amendment's internal §1–§12 numbering scoped within §20 (cited as `§20 →N`).
+
+Cross-Episode Linking & Grouping is organized into the following scopes (the reference deployment's adapter guide, `IMPLEMENTATION-CROSS-EPISODE-LINKING.md`, which lives with that adapter, follows the same order):
+
+| Scope | Coverage | Vector Prefix |
+|-------|----------|---------------|
+| Cross-episode link schema + integrity | `EpisodeLink` hash, mutual exclusivity, audit deltas | `CEL-` |
+| Link health & quarantine lifecycle | Health-state FSM, quarantine resolution/escalation | `LH-` |
+| Inference signals & discovery | `Signal` recording, propose/reject audit events | `SG-` |
+| Episode membership | `MembershipRecord` hash + succession chain | `MR-` |
+| Grouping conformance | `ConformanceDeclaration` hash + SemVer versioning | `CD-` |
+
+All hex values lowercase. All string fields UTF-8. Datetimes UTC-normalized ISO 8601. Floats canonicalized via Python `repr()` semantics (round-trippable, platform-stable).
+
+> **Governance model note.** Unlike the BFM family (SPEC §19, G-19–G-35), Cross-Episode Linking & Grouping has **zero numbered SPEC G-rules**. Its governance is enforced through (a) the `LinkGovernanceError` taxonomy (mutual exclusivity), (b) the Link Health / quarantine FSM (§20 →6, →11.3), (c) the immutable-with-succession chain-integrity checks for `MembershipRecord` / `ConformanceDeclaration`, and (d) the `GroupingGovernanceError` SemVer taxonomy. The governance matrix in §7 reflects THIS structure, not invented G-numbers.
+
+---
+
+## 2. Cross-Episode Link Vectors (§20 →2, →3, →5)
+
+### 2.1 Hash Canonicalization
+
+**CEL-001** — `EpisodeLink` content hash
+- **Class:** REQUIRED — *4.x form, for links written before astp 0.5.0; the 5.0.0 construction is `EPISODE_LINK:v2:` over the §5.1.1 field encoding (SPEC §20 →2)*
+- **Spec Reference:** §20 →2 (hash preimage note)
+- **Description:** `compute_episode_link_content_hash()` MUST produce identical bytes across implementations given identical inputs. The canonical layout is the ordered field set, serialized as a JSON object with `sort_keys=False` and `separators=(",",":")`, then SHA3-256. Field order (from `_HASH_PREIMAGE_FIELDS`): `link_id`, `source_episode`, `target_episode`, `created_at`, `created_by`, `link_type`, `link_strength`, `is_inferred`, `inference_signals`, `inference_threshold`, `retroactive`, `health_state`, `health_checked_at`, `source_version`, `target_version`, `quarantine_reason`, `quarantined_at`.
+- **Verification Protocol:** Cross-implementation consistency check. Two conforming implementations MUST produce identical `content_hash` bytes for the same input tuple.
+- **Failure Condition:** Divergent bytes indicate a canonicalization error (wrong field order, alphabetical key sort, non-`repr` float encoding, non-UTC datetime, or an unexpectedly included/excluded field).
+
+**CEL-002** — Quarantine-resolution field exclusion
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →2 (hash preimage note)
+- **Description:** `quarantine_resolved_at` and `quarantine_resolution` MUST NOT appear in the `EpisodeLink` content-hash preimage. Setting either field on an existing link (on quarantine close) MUST NOT change `content_hash`.
+- **Failure Condition:** A link's `content_hash` changes when only `quarantine_resolved_at` / `quarantine_resolution` are set — the resolution lifecycle is committed by the audit log, not the content hash.
+
+**CEL-003** — Health-state field inclusion
+- **Class:** REQUIRED — *4.x form only; under `EPISODE_LINK:v2:` (SPEC §20 →2) `health_state` and `health_checked_at` are OUT of the preimage and re-stamping after a health transition MUST NOT change `content_hash`*
+- **Spec Reference:** §20 →2, §20 →11.2.2 (`LINK_INTEGRITY` field snapshot)
+- **Description:** Mutable health fields `health_state` and `health_checked_at` ARE part of the preimage (drift detection is cryptographically anchored to write-time state). The `LINK_INTEGRITY` proof's `field_snapshot` MUST cover exactly the CEL-001 field set. Re-stamping after a health transition MUST yield a new, deterministic hash.
+- **Verification Protocol:** Recompute over stored canonical fields; MUST equal stored `content_hash`.
+
+**CEL-004** — `LinkAcceptedDelta` audit binding
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →5, §20 →11.4
+- **Description:** Asserting a link (`assert_episode_link`) MUST emit a `LINK_ACCEPTED` `AuditRecord` on the **source-episode** chain, carrying forward delta (`link_id`, `source_episode`, `target_episode`, `link_type`, `link_strength`, `is_inferred`, `retroactive`) and reverse delta (`reverse_delete_link_id`). The record's `record_hash` MUST chain off `prior_audit_hash` and recompute deterministically.
+- **Failure Condition:** A link node created with no corresponding `LINK_ACCEPTED` audit record, or an audit record whose recomputed hash diverges from stored.
+
+### 2.2 Mutual-Exclusivity Governance (§20 →3)
+
+**CEL-005** — Link-type mutual exclusivity
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →3 (Link Type Taxonomy)
+- **Description:** `enforce_link_mutual_exclusivity()` MUST raise `LinkGovernanceError` when a new link type collides with an existing type on the same `(source_episode, target_episode)` pair. The exclusion set is exactly `{CONTINUES_FROM, SUPERSEDES}` and `{CONTINUES_FROM, BRANCHES_FROM}`. `SUPERSEDES` and `BRANCHES_FROM` MUST coexist; all other types compose freely.
+- **Failure Condition:** A `(source, target)` pair carries both `CONTINUES_FROM` and `SUPERSEDES` (or both `CONTINUES_FROM` and `BRANCHES_FROM`), or a valid compatible pair is spuriously rejected.
+
+**CEL-006** — Endpoint existence precondition
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →2, IMPLEMENTATION §4.4
+- **Description:** A link assertion whose source or target Episode does not exist MUST be rejected before any node/edge write (no orphan links). The `LINKED_TO {via: link_id}` edge MUST carry the link_id for one-hop edge→node lookup.
+
+**CEL-007** — Resumption isolation rule
+- **Class:** RECOMMENDED
+- **Spec Reference:** §20 →3 (Resumption isolation rule)
+- **Description:** On episode resumption the loader MUST follow `CONTINUES_FROM` and `SUPERSEDES` links (spine traversal) and MAY follow `INFORMED_BY` / `SPAWNED_FROM` up to one hop. `REFERENCES` links are non-loading — available for audit but MUST NOT trigger content retrieval on resumption.
+
+---
+
+## 3. Link Health & Quarantine Vectors (§20 →6, →11.3)
+
+**LH-001** — Health-state FSM
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →6 (Link Health State Machine)
+- **Description:** The health FSM MUST admit exactly the transitions in §20 →6: `VALID → {STALE, FROZEN, BROKEN, QUARANTINED}`, `STALE → {BROKEN, QUARANTINED}`, `QUARANTINED → {VALID (CONFIRMED), BROKEN (DISSOLVED), ESCALATED (TTL)}`, `BROKEN → QUARANTINED (re-evaluation)`. There is NO automatic `QUARANTINED → BROKEN`; exit requires an explicit `QuarantineResolution`.
+- **Verification Protocol:** Given a state and a transition trigger, the resulting state MUST match the FSM; illegal transitions MUST be rejected, not silently applied.
+- **Failure Condition:** A quarantined link auto-transitions to `BROKEN` without an explicit resolution, or a major-version target advance auto-transitions to `BROKEN` (it MUST route to human review, remaining `VALID`/`STALE`).
+
+**LH-002** — Quarantine resolution semantics
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →11.3.1, `QuarantineResolution` enum
+- **Description:** `CONFIRMED` → `health_state = VALID`; `DISSOLVED` → `health_state = BROKEN`; both set `quarantine_resolved_at` + `quarantine_resolution` and emit `LINK_QUARANTINE_RESOLVED`. `ESCALATED` keeps `health_state = QUARANTINED` and emits `QUARANTINE_ESCALATED`. Escalated links MUST NOT auto-resolve — human review is required to reach `CONFIRMED`/`DISSOLVED`.
+
+**LH-003** — Per-Episode quarantine queue
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →11.1.4 (ephemeral coordinator, quarantine queue scope)
+- **Description:** The quarantine queue MUST be scoped per Episode and ordered by quarantine deadline. How the coordinator represents it — key names, data structure — is an implementation choice. A single global queue across all Episodes is non-conforming.
+- **Failure Condition:** A single global quarantine queue is used, causing a quarantine event in one Episode to be processed in another's context.
+
+**LH-004** — Quarantine escalation event
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →11.3.3 (quarantine escalation)
+- **Description:** On TTL breach a `QUARANTINE_ESCALATED` audit event MUST fire carrying `link_id`, `episode_id`, `quarantined_at`, `ttl_deadline`, `escalated_at`, `escalation_reason ∈ {TTL_EXCEEDED, INTEGRITY_UNRESOLVABLE, HUMAN_REQUIRED}`. The link remains `QUARANTINED`.
+
+---
+
+## 4. Inference Signal & Discovery Vectors (§20 →4, →5, →12.2)
+
+**SG-001** — `Signal` recording completeness
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →4 (Inference Signal Specification)
+- **Description:** Every signal contributing to a candidate's composite score MUST be recorded in `inference_signals` with `signal_type ∈ {SEMANTIC_SIMILARITY, PARTICIPANT_OVERLAP, TEMPORAL_PROXIMITY, EXPLICIT_REFERENCE, SHARED_ARTIFACT}`, `signal_weight`, `signal_value`, `computed_at`. Signals are canonicalized into the CEL-001 preimage via `model_dump()` (recursively, in list order). Signal **combination** (weights, composite formula) is behavioral-tier (sovereign); signal **recording** is required.
+- **Failure Condition:** A composite score computed from a signal not present in the recorded `inference_signals` list.
+
+**SG-002** — `LINK_PROPOSED` audit-the-decision
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →5, §20 →12.2, §1 (constants)
+- **Description:** `propose_link_candidate()` (score in `[DISCOVERY_THRESHOLD, AUTO_ACCEPT_THRESHOLD)`) MUST emit an append-only `LINK_PROPOSED` audit event carrying `composite_score`, the full `inference_signals` breakdown, and `discovery_threshold_at_creation` + `auto_accept_threshold_at_creation` (the threshold values in effect at proposal time). No `EpisodeLink` node is created. The returned `audit_id` correlates later accept/reject decisions.
+- **Failure Condition:** A proposal that omits the threshold-at-creation values, defeating post-hoc calibration.
+
+**SG-003** — `CANDIDATE_REJECTED` sub-threshold recording
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →5 (CANDIDATE_REJECTED note), §1
+- **Description:** `record_candidate_rejection()` (score strictly `< DISCOVERY_THRESHOLD`) MUST emit an append-only `CANDIDATE_REJECTED` audit event with full signals + `discovery_threshold_at_creation`. Not surfaced for human review; exists purely so the calibration loop can analyze sub-threshold patterns.
+
+**SG-004** — `LINK_REJECTED` proposal correlation
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →5, `RejectionReason` enum
+- **Description:** `record_link_rejection()` MUST emit `LINK_REJECTED` carrying `proposed_audit_event_id` (the `LINK_PROPOSED` it rejects) and `rejection_reason ∈ {LOW_CONFIDENCE, WRONG_RELATIONSHIP_TYPE, NOT_RELATED, DUPLICATE_OF_EXISTING}`. Rejection is a new forward event (append-only) — it MUST NOT mutate or delete the prior proposal record.
+- **Failure Condition:** A rejection that overwrites the proposal, or omits the `proposed_audit_event_id` linkage.
+
+---
+
+## 5. Episode Membership Vectors (§20 →7, →11.3.2)
+
+### 5.1 Hash Canonicalization
+
+**MR-001** — `MembershipRecord` content hash
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →7, §20 →10 (forward-pointer exclusion)
+- **Description:** `compute_membership_record_content_hash()` canonicalizes, in order (from `_MEMBERSHIP_HASH_PREIMAGE_FIELDS`): `record_id`, `episode_id`, `group_id`, `group_system`, `asserted_at`, `asserted_by`, `membership_role`, `supersedes_record_id`, `succession_reason`. Same §3-canonicalizer (SHA3-256, `sort_keys=False`) as CEL-001. `membership_role` is INCLUDED: role is content, so a role change requires a new record via succession.
+- **Verification Protocol:** Cross-implementation consistency check. Two conforming implementations MUST produce identical bytes for the same input tuple.
+- **Failure Condition:** `membership_role` omitted from the preimage (would let a role edit go uncommitted), or `superseded_by_record_id` included (would invalidate a sealed record's hash on later succession).
+
+**MR-002** — Forward-pointer exclusion
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →10, §20 →11.3.2
+- **Description:** `superseded_by_record_id` MUST NOT appear in the `MembershipRecord` preimage. Setting it (when a later record supersedes this one) MUST NOT change this record's `content_hash`.
+- **Failure Condition:** A prior record's `content_hash` changes when its `superseded_by_record_id` forward pointer is set during succession.
+
+### 5.2 Succession Chain
+
+**MR-003** — Immutable-with-succession chain integrity
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →7 (Immutability rule), §20 →11.3.2
+- **Description:** `MembershipRecord` is append-only. A successor with `supersedes_record_id` set MUST be rejected unless the prior exists, is not already superseded, and shares the same `episode_id` + `(group_id, group_system)`. On success, `(new)-[:SUPERSEDES]->(prior)` is wired and the prior's `superseded_by_record_id` forward pointer is set. The **active** record for a `(episode_id, group_id, group_system)` tuple is the one with no `superseded_by_record_id`.
+- **Failure Condition:** A prior record superseded twice, a cross-group/cross-episode succession accepted, or a prior record deleted/modified in place.
+
+**MR-004** — `MEMBERSHIP_CHAIN` proof
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →11.2.3
+- **Description:** A `MEMBERSHIP_CHAIN` proof MUST re-verify the ordered `content_hash` of each record oldest-first and identify the single active (terminal) record. Any broken link or invalid hash MUST yield `BROKEN_CHAIN` / `INVALID`.
+
+**MR-005** — Membership audit events
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →11.4
+- **Description:** `assert_membership_record()` MUST emit `MEMBERSHIP_RECORD_CREATED` unconditionally, and additionally `MEMBERSHIP_RECORD_SUPERSEDED` on any succession — carrying `old_role` + `new_role` so role-change history is queryable from the audit log alone. The `SUPERSEDED` record MUST chain directly off the `CREATED` record's `record_hash` (both describe one operation).
+
+---
+
+## 6. Grouping Conformance Vectors (§20 →8, Appendix A)
+
+### 6.1 Hash Canonicalization
+
+**CD-001** — `ConformanceDeclaration` hash
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →8, §20 →10
+- **Description:** `compute_conformance_declaration_hash()` canonicalizes, in order (from `_DECLARATION_HASH_PREIMAGE_FIELDS`): `declaration_id`, `group_id`, `group_system`, `declared_at`, `declared_by`, `declaration_version`, `capabilities`. Same §3-canonicalizer. `capabilities` is a `list[Capability]`; each canonicalizes via `model_dump()` (recursively, in list order — `capability_id` + `description`). `superseded_by` is EXCLUDED (forward pointer, §20 →10).
+- **Verification Protocol:** Cross-implementation consistency check. Two conforming implementations MUST produce identical bytes for the same input tuple.
+- **Failure Condition:** `superseded_by` included, capability ordering not preserved, or field order divergence.
+
+### 6.2 SemVer Governance
+
+**CD-002** — SemVer format enforcement
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →8
+- **Description:** `enforce_semver_format()` MUST reject any `declaration_version` that is not a strict `major.minor.patch` non-negative triplet (pre-release / build-metadata suffixes rejected), raising `GroupingGovernanceError`.
+
+**CD-003** — Version-bump classification
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →8 (version semantics table), Appendix A
+- **Description:** `classify_version_bump(old, new)` MUST require `new > old` strictly (raise otherwise) and return `"major"` (major component changed), `"minor"` (minor changed), or `"patch"`. Level-skips (e.g. 1.0.0 → 3.0.0) are accepted as their highest changed component. Major → breaking; minor/patch → compatible.
+- **Failure Condition:** A non-increasing version accepted, or a bump misclassified against the §20 →8 table.
+
+**CD-004** — Bump audit-event selection
+- **Class:** REQUIRED
+- **Spec Reference:** §20 →11.4, §20 →8
+- **Description:** `bump_conformance_declaration()` MUST emit `DECLARATION_SUPERSEDED` for a major bump and `DECLARATION_VERSION_BUMPED` for a minor/patch bump, wire `(old)-[:SUPERSEDED_BY]->(new)`, set the prior's `superseded_by` forward pointer, and anchor the audit event to the synthetic chain key `declaration:{group_system}:{group_id}`. Initial `register_conformance_declaration()` MUST NOT fire an audit event (only bumps do).
+- **Failure Condition:** A major bump emitting `DECLARATION_VERSION_BUMPED` (or vice versa); an initial registration firing a spurious event; declaration events anchored to an episode chain instead of the synthetic key.
+
+**CD-005** — Breaking-change reference (Appendix A)
+- **Class:** RECOMMENDED
+- **Spec Reference:** §20 Appendix A
+- **Description:** Implementations SHOULD classify as **major** any change that renames/removes/retypes a field appearing in a `content_hash` preimage, or changes the hash algorithm / canonical serialization; as **minor** any new optional field, new `LinkType`, new `AuditEventType`, or new `LinkHealthState`; as **patch** documentation/threshold/editorial changes.
+
+---
+
+## 7. Governance Enforcement Matrix
+
+Cross-Episode Linking & Grouping has **no numbered SPEC G-rules**. Governance is enforced via error taxonomies, the health/quarantine FSM, and succession-chain integrity. This matrix maps each enforcement mechanism to its vector(s).
+
+| Mechanism | Enforcement surface | Vector(s) |
+|-----------|---------------------|-----------|
+| Link mutual exclusivity | `LinkGovernanceError` (`enforce_link_mutual_exclusivity`) | CEL-005 |
+| Endpoint existence | `ValueError` in `write_episode_link_sync` | CEL-006 |
+| Quarantine-field hash exclusion | `_HASH_PREIMAGE_FIELDS` (§20 →2) | CEL-002 |
+| Link health FSM | Health-state transition rules (§20 →6) | LH-001, LH-002 |
+| Per-Episode quarantine queue | Coordinator queue scope (§20 →11.1.4) | LH-003 |
+| Quarantine escalation | `QUARANTINE_ESCALATED` (§20 →11.3.3) | LH-004 |
+| Signal recording | Audit-the-decision (§20 →4, →12.2) | SG-001, SG-002, SG-003, SG-004 |
+| Membership hash inclusion/exclusion | `_MEMBERSHIP_HASH_PREIMAGE_FIELDS` (§20 →7, →10) | MR-001, MR-002 |
+| Membership succession integrity | Chain checks in `write_membership_record_sync` | MR-003, MR-004, MR-005 |
+| Declaration forward-pointer exclusion | `_DECLARATION_HASH_PREIMAGE_FIELDS` (§20 →8, →10) | CD-001 |
+| SemVer governance | `GroupingGovernanceError` (`enforce_semver_format` / `classify_version_bump`) | CD-002, CD-003, CD-004 |
+
+---
+
+## 8. Conformance Levels
+
+### Level 1: Protocol Conformance (Wire + State tiers)
+
+Implementation passes all **REQUIRED** vectors in sections 2–6 and the governance matrix in section 7. This makes two implementations interoperable — they can exchange `EpisodeLink`, `MembershipRecord`, and `ConformanceDeclaration` structures and verify each other's hashes (wire tier, §20 →12.1), and their audit logs are comparable (state tier). No claim is made about storage layout, embedding model, or scoring algorithm.
+
+### Level 2: Full Conformance
+
+Level 1 plus all **RECOMMENDED** vectors (CEL-007 resumption isolation, CD-005 breaking-change classification) and the storage-architecture obligations of §20 →11.1 / →11.5 (write-order invariant, active-record index, consistency-window SLA).
+
+### Behavioral tier (sovereign — no conformance requirement)
+
+Signal-combination algorithm, embedding-model selection, threshold-calibration strategy, and internal indexing are implementation decisions (§20 →12.1). The protocol requires only that the *decision* is recorded (audit-the-decision, §20 →12.2), which is covered by the `SG-` vectors.
+
+---
+
+## 9. Cross-Reference
+
+- **SPEC.md §20** — normative protocol surface (v3.2.1); internal §1–§12 numbering cited as `§20 →N`.
+- **IMPLEMENTATION-CROSS-EPISODE-LINKING.md** — the reference deployment's adapter guide (non-normative; shipped with that adapter, not with the protocol).
+- **CONFORMANCE-BFM.md** — sibling BFM vector set (SPEC §19); shares the cross-implementation-consistency vector format.
+- **`astp/core/hash_canonical.py`** — the shared canonicalizer that every `CEL-`/`MR-`/`CD-` hash vector references.
+
+---
+
+*ASTP Cross-Episode Linking & Grouping Conformance Test Vectors are maintained by Scorched Earth Labs.*
+*Vector set version: 1.0.0 | Applies to SPEC.md: v3.2.1 §20*