Skip to content

Final-system design mirror · Canonical source: docs/target/functional-chains/chains/FC-02-source-custody.md · SHA-256 7443af754d4f3b6561733305332cc9512e3d7ca0eb0ad3082581512c678d7578. Design intent is not deployment proof.

FC-02 — Durable source, snapshot and representation custody

Classification: TARGET_DESIGN — final-system requirement, not proof of integration or deployment.

Inherits: System model, authority, contracts and receipts, failure rules.

Functional promise

Owner(s): Mediatheque / Mediatheque-blank.

Initiator: A permitted source provider deposits reviewed evidence into the selected library instance.

Expected result: Custody receipt and immutable source/snapshot/representation references under library ACL.

Nominal end-to-end behavior

Step Stage Required outcome
1 Authorize deposit Scoped owner state and evidence receipt; no hidden mutation of other systems
2 checksum source Scoped owner state and evidence receipt; no hidden mutation of other systems
3 preserve version Scoped owner state and evidence receipt; no hidden mutation of other systems
4 issue receiver receipt Scoped owner state and evidence receipt; no hidden mutation of other systems
5 serve permission-filtered references. Scoped owner state and evidence receipt; no hidden mutation of other systems

Interfaces and authority gates

Target boundary references: B-KNOW-01, B-KNOW-02. These identify candidate or scoped adopted contracts; they do not certify complete multi-owner deployment. Producer disclosure and receiving-owner admission are separate decisions.

Where no exact interface is adopted, keep TBD rather than inventing a protocol ID. All privileged effects must be checked at the actual enforcing owner.

Failure, privacy and forbidden shortcuts

Reject modified bytes, conflicting replay and cross-instance private reads; custody never validates epistemic truth.

Owner-specific tenant/actor identity, source classification, integrity checks, replay and correction must be preserved. No debug dashboard or public documentation site may disclose private content.

Definition of done — acceptance and negative tests

Same-intent replay yields same receipt; divergent replay denied; permissioned recovery works.

To qualify the full chain, pin both producer and consumer revisions and execute negative fixtures, recovery and idempotency scenarios. An owner code snapshot alone does not demonstrate running behavior.

Required code and contract alignment

Pin Skope sender and Mediatheque receiver schema and prove durable storage plus isolated library instance.

Source anchors and verification boundary

See the 53-repository portfolio and snapshot reconciliation for source member names, hashes, declared local roots and evidence limitations. Contract boundaries are catalogued in the C0 target ledger. This is intended final behavior, not evidence of a currently operational multi-repository integration.