The Magenta Development Kit (MDK) is the mandatory ritual through which software artifacts become eligible for execution under the Magenta governance runtime. Without MDK initialization and a committed baseline epoch, execution is blocked regardless of other licenses. MDK is the structural gate key that connects artifact conformance to runtime execution authority.
- MDK initialization establishes the first baseline epoch (E1)
- Without MDK, execution is blocked even with Platform and Primitive licenses
- MDK enforces structural primitives: StructuralArtifact, ExecutableUnit, EligibilityGate
MAGENTA DEVELOPMENT KIT
The Gate Key
MDK is mandatory for execution eligibility. Platform and Primitive licenses are valid without MDK, but execution is blocked. MDK is the gate key.
What MDK Provides
The MDK provides structural primitives and scaffolding that make software artifacts legible to the Magenta governance runtime, enabling execution eligibility assessment.
-
Structural Primitives
StructuralArtifact, ExecutableUnit, EligibilityGate — the building blocks of governed execution.
-
Conformance Rules
Pre-built validation rules. No unresolved TODOs. No console logs. Structural discipline.
-
Epoch Integration
Birth into the runtime. Baseline establishment. History initialization.
-
CLI Tools
magenta validate, magenta baseline, magenta status. Command-line governance.
The Ritual
MDK is not optional tooling. It is the mandatory ritual through which artifacts become eligible for execution in the Magenta governance runtime.
- 1. Initialize MDK in your project
- 2. Define structural artifacts
- 3. Configure conformance rules
- 4. Establish baseline epoch
- 5. Execution becomes possible
MDK and the Platform
MDK licenses grant execution eligibility at the artifact level. The Platform provides the runtime governance substrate that evaluates and enforces that eligibility in real time.
See the Canon Laws for the governance invariants that MDK and Platform together enforce. View pricing for licensing details.