Final-system design mirror · Canonical source:
docs/target/functional-chains/chains/FC-11-learning-delivery.md· SHA-256ef3bbb446e1a0cf461309636951183d802babf55dcd4d8ded34171f83a32028c. Design intent is not deployment proof.
FC-11 — Neutral education engine and institutional projections
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): Ekole / Ekole-Pastorale / UCKK-Assets / UCKK-Ops-Console.
Initiator: An educational authority approves a content pack and optional institutional projection.
Expected result: Rebuildable learning experience and permissioned Moodle/institution receipt.
Nominal end-to-end behavior
| Step | Stage | Required outcome |
|---|---|---|
| 1 | Validate pack | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 2 | import | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 3 | class preview | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 4 | institution consent | Scoped owner state and evidence receipt; no hidden mutation of other systems |
| 5 | optional Moodle write | 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-EDU-04. 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
Preview never writes to Moodle; a media reference grants no private library access.
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
Idempotent approved import and denial of unapproved course/tenant operations.
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 content-pack, media and institutional write/projection contracts with owner consent.
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.