MDK is internal architecture reference material describing how the Magenta trust core reasons about an artifact's eligibility — it is not a required public runtime, not something an evaluator installs, and not the product Magenta Canon sells. The product is a verifiable MCP accountability gateway that governs an AI agent's tools/call at the tool boundary and produces independently verifiable evidence of each decision. MDK is deliberately secondary to that, kept public for readers who encounter its vocabulary in older documents.
- Enforced runtime today: default-deny gating of the MCP tools/call method class, with signed, hash-chained receipts for allow and block alike
- MDK is a modelling vocabulary — baselines, structural hashes, conformance state — not a mechanism the gateway imposes on a customer's systems
- There is no public package, no initialization command an evaluator must run, and no loss of function if an organization stops using Magenta
ARCHITECTURE REFERENCE
MDK — an internal reference model, not the product
If you are here to judge the product, the proof walkthrough is the page you want. MDK is background architecture material and is not a required public runtime.
Keep Three Things Apart
What is enforced in runtime today: the MCP gateway evaluates a tools/call against operator-delegated capability grants and hard ceilings, default-deny, before the call reaches the downstream tool, and records every allow and block as a signed, hash-chained receipt. That path — and only that path — is the product's enforced runtime.
What MDK is: an internal architectural model relating an artifact's structure to execution eligibility — a committed baseline, a structural hash, and a conformance state the trust core can reason about. It is reference material.
What MDK is not: it is not a required public runtime, not a step in evaluating Magenta, not a licensing mechanism, and not a condition of using the gateway. A document describing a mechanism is not evidence that the mechanism runs.
Vocabulary You May Meet in Older Material
Baseline epochs — the reference model records conformance points as append-only, hash-linked baselines rather than version numbers. This is internal record-keeping in the architecture material, not the enforced authority mechanism.
Execution eligibility — in the reference model, an artifact without a committed baseline is not treated as eligible. This describes how the model reasons; it is not a runtime lock and imposes nothing on a customer's systems.
Structural primitives — StructuralArtifact, ExecutableUnit, and EligibilityGate are modelling vocabulary from the same material, named here so a reader who meets them elsewhere knows where they belong.
Where the Product Story Is
An allowed action, a blocked action, the downstream tool's own log showing the blocked call never arrived, an independent verification, and a tampered bundle that fails. That is what there is to evaluate.
See the proof walkthrough, the platform architecture, and the Canon for the operating principles. Evaluation access is described on the design-partner evaluation page; there is no public package and no licensing tier to select.