Status: Accepted Date: 2026-09-20 Related: MTP implementation plan, ADR-A25, ADR-A42, ADR-A43 Numbering note: The LATTICE platform epic’s Phase 0 plan refers to a separate, unrelated decision (Control Plane HTTP runtime: virtual threads, minimal server, deadline propagation) as “ADR-A44 amended.” That content does not amend this ADR — it is filed as ADR-A81 to avoid collision with this accepted decision.
MTP consumes normative MORK ontology, MCN codebook, decoder, examples, and shapes to generate a versioned curriculum. It must remain reproducible and structurally verifiable without depending on an LLM backend. Curated doctrine, lens, cassette, partition, and routing material also needs a clear ownership boundary from generated output.
Place MTP Python code under tools/mork/src/mtp/, curated content under ontology/mork/mtp/data/, and generated committed output under ontology/mork/mtp/out/. MTP consumes mcn, mcn_codebook, Mork.ttl, examples, and constraints through adapters. It does not modify those sources except through separately approved work.
Use root mise for scoped MTP bootstrap, check, and build tasks. Add a manual MTP structural CI job that installs the MORK package, runs structural tests, regenerates the pack, checks it, and fails on generated-output or pin drift. Backend-dependent model-quality evaluation remains deferred.