Final-system design mirror · Canonical source:
docs/target/functional-chains/chains/FC-08-governed-execution.md· SHA-2562255e2de6802e726961e7649446c228d11b9ef9a032a97efbe587a7cd972c2d4. Design intent is not deployment proof.
FC-08 — Durable operational execution and accountability
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): Orgo / Konnaxion / Interaction-Kernel.
Initiator: A trusted owner submits a typed intent for real work under actual permission.
Expected result: Receiver-owned Case/Task and reconciled terminal effects; optional civic accountability.
Nominal end-to-end behavior
| Step | Stage | Required outcome |
|---|---|---|
| 1 | Validate intent | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 2 | create Signal/Case/Tasks | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 3 | journal outbox | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 4 | execute | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 5 | reconcile | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 6 | publish terminal impact. | 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-EDU-02, B-EDU-03. 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
Acceptance is not success; retries cannot duplicate external effects; unauthorized preview produces no Task.
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
Crash/replay, changed-intent conflict, owner PEP denial and terminal impact tests.
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
Preserve Orgo ownership and two-sided IK test fixtures; adopt separate educational intent only with owner approval.
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.