Skip to content

Final-system design mirror · Canonical source: docs/target/functional-chains/chains/FC-23-external-interop.md · SHA-256 97ee708406429e320fce925fa21c61b966cb2c45e0a3d9dde76f0fd9705a57ed. Design intent is not deployment proof.

FC-23 — Typed owner-to-owner and third-party exchange

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): Interaction-Kernel / Daat / two actual owner products.

Initiator: Two parties adopt an exact bounded contract for an identity-scoped exchange.

Expected result: Receiver-owned admission and terminal effect receipt, or an explicit rejection.

Nominal end-to-end behavior

Step Stage Required outcome
1 Agree profile Scoped owner state and evidence receipt; no hidden mutation of other systems
2 authenticate Scoped owner state and evidence receipt; no hidden mutation of other systems
3 map allowed fields Scoped owner state and evidence receipt; no hidden mutation of other systems
4 validate Scoped owner state and evidence receipt; no hidden mutation of other systems
5 execute owner effect Scoped owner state and evidence receipt; no hidden mutation of other systems
6 reconcile. Scoped owner state and evidence receipt; no hidden mutation of other systems

Interfaces and authority gates

Target boundary references: B-CIVIC-01, B-CIVIC-02, B-SEC-01. 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

No global mandatory bus, unauthenticated mapping or sender direct-write to receiver database.

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

Golden/invalid envelope, downgrade, replay conflict and PEP denial fixtures.

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

Introduce adopted profile ID only after bilateral owner review and a passing consumer test.

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.