Skip to content

Final-system design mirror · Canonical source: docs/target/functional-chains/04-cross-chain-compositions.md · SHA-256 816a6ba5588a55669e4feaffb500542b02c021ea8cf16182ec0d232a9c8f895d. Design intent is not deployment proof.

04 — Cross-chain scenarios

Status: TARGET_DESIGN.

Knowledge: FC-01→FC-02→FC-03→FC-04→FC-05→FC-06, with explicit reviews and separate publication permission. Civic: FC-07→FC-08 with IK where adopted; terminal effect returns to Konnaxion. Education: FC-10→FC-11, with optional governed Orgo intent only after teacher approval. Language: FC-04/other approved typed input→FC-12→FC-13→FC-22. Agentic: FC-15→FC-14→effect owner, never direct DB edits. Offline: FC-04→FC-19→FC-06 without public Git. Creative: FC-21→FC-10→FC-11 with rights review. Operations: FC-18 and FC-24 prove safe failure and recovery.

Each named scenario must pin both endpoints, run valid/invalid fixtures, record actual receipts and disclose unsupported paths.

Functional chain index · Repository coverage · Acceptance