Skip to content

Final-system design mirror · Canonical source: docs/target/functional-chains/README.md · SHA-256 1b4e17731d349b60ff8bdab680328c8175446023ad4a20ae9e4606cf28997635. Design intent is not deployment proof.

Final-system functional chains — 24 capabilities

Status: TARGET_DESIGN. This is a cumulative and compositional final-system specification; it is not a claim that all interfaces are deployed.

Cumulative reading order

  1. System model — common trust and state principles.
  2. Authority and ownership — who may change state.
  3. Contracts and receipts — handoff schema and idempotency.
  4. State, trust and failure — lifecycle and denial.
  5. Each functional chain below, then cross-chain scenarios.
  6. 53-repository coverage, qualification, code alignment, glossary, deployment profiles, quality requirements and boundary traceability.

Functional chain catalogue

Chain Intended capability
FC-01 Bounded research and noncanonical acquisition
FC-02 Durable source, snapshot and representation custody
FC-03 Mapping, reviewed external alignment and lexicon
FC-04 Canonical Kristal authoring and conformance
FC-05 Independent qualification and immutable knowledge publication
FC-06 Read-only knowledge consumers and context views
FC-07 Civic participation and finalized decisions
FC-08 Durable operational execution and accountability
FC-09 World and Universe context releases
FC-10 Pedagogical situations, plans and supervised missions
FC-11 Neutral education engine and institutional projections
FC-12 Faithful multilingual realization and grammar runtime
FC-13 Editorial documents and reviewed multilingual publication
FC-14 Scoped identity, policy and actual enforcement
FC-15 Bounded agentic planning and approved owner effects
FC-16 Build, runtime admission, deploy and rollback
FC-17 Optional Koali Space app navigation
FC-18 Independent diagnostics and time-scoped evidence
FC-19 Portable integrity packages and static reading
FC-20 Medical knowledge under separate safety governance
FC-21 Licensed characters, palettes and educational media
FC-22 Public discovery, docs portal and explanatory scenarios
FC-23 Typed owner-to-owner and third-party exchange
FC-24 Observability, incident containment and owner recovery

System-level interpretation

A local authoring workspace does not require public Git. Civic decisions do not require semantic compilation. Educational previews do not create Orgo Tasks or write to Moodle. An optional Koali shell does not grant business rights. Source custody and epistemic validation are distinct owner decisions.

The 26 C0 boundaries are proposed architectural interfaces, not proof of completed deployment. Read the source-based status before making implementation claims.