Skip to content

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

Target code-alignment instructions

Type: owner-level implementation instructions for the final system. The 53 owner code snapshots are evidence of supplied bytes, not 53 tested integrations. C0 may modify documentation/coordination code; external owner code changes require complete source trees, bilateral adoption and suitable tests.

Change order

  1. P0 source intake: Skope and Médiathèque must agree on noncanonical source package, receiver-owned custody receipt, checksum, provenance, access scope and replay conflict rules. DaaT must preserve explicit review and host-injected policy gates.
  2. P0 semantics: Framework v11, Kit v4, diK, Kristalizer and Pack must pin compatible exact versions. Reject external Q/P as canonical KQ/KP and prohibit implicit semantic/lexical writes.
  3. P0 release/read: owner approval, KristalDiag exact-input evidence and immutable publication must be independently checked before Pack/Kompiler/EncyKlopedia/Konstellation can import an authorized derived view.
  4. P0 civic: Konnaxion↔Orgo adopted IK profiles require durable idempotency, terminal reconciliation and correct World/tenant authorization.
  5. P0 public architecture: central documentation, docs portal, homepage and Scenario Mosaic consume a safe read-only metadata manifest, never full source snapshots, private files or inferred deployed states.
  6. P1 education: Kontexte/Kompose/Akor preview and Ékole/UCKK projection must not create real Orgo/Moodle effects without explicit owner approval.
  7. P1 language/platform: qualified RuntimeSet promotion, editorial publication approval, platform PEP, separate ReleaseSet/Space lifecycle and measured rollback.
  8. P2 optional agentic/medical/creative: domain-specific safety, consent/licensing and actual integration profile before deployment claims.

Required owner work package

For each interface: producer, consumer, exact revision/profile pins, authoritative state, identity/tenant/purpose, allowed and denied payloads, source/output digests, idempotency, terminal receipt, privacy, rollback, owner unit tests, cross-owner fixtures, independent check and open decisions.

Current public-facing changes for branch 10 are specified in its integration report. All other owner implementations remain outside this branch's write scope.

See functional code backlog and 26 target boundary definitions. Never silently rewrite frozen historical v6 contract identities to v11.