Skip to content

Final-system design mirror · Canonical source: docs/target/journeys.md · SHA-256 f89ed1d12485994edce5427d604bad86da26b8f3fa8eedac97edfb6c727246cf. Design intent is not deployment proof.

Intended final-system journeys

Status: TARGET_DESIGN — desired capabilities, not asserted end-to-end deployments. The authoritative details, owners and negative tests for each stage live in the linked 24-chain specification.

J1 — Research source to governed public knowledge

FC-01 acquisition → FC-02 custody → FC-03 mapping → FC-04 authoring → FC-05 release → FC-06 reading. Candidate QIDs and extracted labels must be reviewed before semantic authoring. A local build remains private until independently qualified and explicitly authorized for a named publication destination.

J2 — Finalized civic decision to reconciled accountable work

FC-07 Konnaxion → FC-23 adopted IK profile → FC-08 Orgo → terminal impact receipt. Accepted work is not completed work; replay must not double-execute an effect.

J3 — Educational design to optional real work or Moodle projection

FC-10 scenario → FC-11 learning, optionally Orgo under separately approved teacher/institution authority. A simulation/preview creates no real Case/Task or Moodle write. For licensed creative media, include FC-21.

J4 — Language, editorial and public discovery

Approved typed input → FC-12 SemantiK runtime → FC-13 Spek editorial → FC-22 public presence. RuntimeSet qualification, human review, release permission and public site deployment are separate controls.

J5 — Platform admission and recovery

FC-14 identity, FC-18 independent diagnostics, FC-16 host lifecycle and FC-24 recovery. Koali Spaces is an optional presentation shell, not a requirement for domain applications or semantic authoring.

Each journey needs exact versioned owners, producer/consumer acceptance fixtures, owner authorization and terminal receipts before the maturity ledger can claim qualification. See cross-chain compositions.