Observable outcome: KEEP-CATALOG-003 in docs/formats/segment-store-v1/requirements.md points to its actual executable public ordering evidence. At main8d902516e682361882bc5c9902de296ce5c9de85 the ledger names tests/catalog_ordering.rs, which is absent. Actual laws live in tests/catalog/ordering_laws.rs and are included by tests/catalog.rs. This escaped the #69/PR #136 living-documentation review; it is a verified evidence-reference defect, not proof that ordering behavior is missing. Scope: correct this catalog evidence anchor, inspect its claimed ordering/duplicate laws, and verify the named target/module remain executable. Exclusions: no format, identity, runtime publication, or original roadmap criterion/checkbox changes. Acceptance: (1) reference names actual root integration target and ordering module; (2) RED static evidence against current main documents the missing old anchor; (3) GREEN reference and public ordering/duplicate laws pass in copy-isolated Docker debug/release; (4) relevant Markdown/link/whitespace gates pass and issue/PR/mainline integration remain linked. No semantic prerequisites established; shared documentation does not imply dependence on #147 or #146. One independently mergeable documentation correction under audit #131.
Scope reconciliation: the same catalog ledger also names absent tests/catalog_filesystem_publication.rs in KEEP-CATALOG-008. Include correction to its actual executable unit-test owner src/adapters/filesystem_catalog_publisher_tests.rs, which includes the existing filesystem authority/directory/initialization/refusal modules. This is one catalog-evidence anchor outcome; original ordering checks remain required and runtime changes remain excluded. Acceptance additionally requires RED for the absent old owner, GREEN for actual owner/module inclusion, and the16 filesystem publisher laws in Docker debug/release. These fixture laws use a test-only unchecked publisher; do not claim they prove production platform admission.
Observable outcome: KEEP-CATALOG-003 in docs/formats/segment-store-v1/requirements.md points to its actual executable public ordering evidence. At main8d902516e682361882bc5c9902de296ce5c9de85 the ledger names tests/catalog_ordering.rs, which is absent. Actual laws live in tests/catalog/ordering_laws.rs and are included by tests/catalog.rs. This escaped the #69/PR #136 living-documentation review; it is a verified evidence-reference defect, not proof that ordering behavior is missing. Scope: correct this catalog evidence anchor, inspect its claimed ordering/duplicate laws, and verify the named target/module remain executable. Exclusions: no format, identity, runtime publication, or original roadmap criterion/checkbox changes. Acceptance: (1) reference names actual root integration target and ordering module; (2) RED static evidence against current main documents the missing old anchor; (3) GREEN reference and public ordering/duplicate laws pass in copy-isolated Docker debug/release; (4) relevant Markdown/link/whitespace gates pass and issue/PR/mainline integration remain linked. No semantic prerequisites established; shared documentation does not imply dependence on #147 or #146. One independently mergeable documentation correction under audit #131.
Scope reconciliation: the same catalog ledger also names absent tests/catalog_filesystem_publication.rs in KEEP-CATALOG-008. Include correction to its actual executable unit-test owner src/adapters/filesystem_catalog_publisher_tests.rs, which includes the existing filesystem authority/directory/initialization/refusal modules. This is one catalog-evidence anchor outcome; original ordering checks remain required and runtime changes remain excluded. Acceptance additionally requires RED for the absent old owner, GREEN for actual owner/module inclusion, and the16 filesystem publisher laws in Docker debug/release. These fixture laws use a test-only unchecked publisher; do not claim they prove production platform admission.