MDAAI
MDAAI is a protocol for governing AI-assisted development. Choose and configure a template to apply its rules for authority, scope, evidence and review.
By Eris Margeta Kurdali · Repository

Read the paper
MDAAI: A Protocol for Governing AI-Assisted Development
Download paper (PDF)Three pages · Preprint / documentary design paper · Eris Margeta Kurdali · Published 2026-10-05. Soft edition: simulated print finish, not a genuine scan.
Apply the protocol with a template
To apply the protocol, choose and configure a template. A template supplies the concrete governance files; agents, coding harnesses and execution tools are separate layers. The protocol defines a method for authority, scope, evidence, history and review—not an executor. The templates documented here put that method in Markdown and JSON files alongside your project.
Choose a templateSee the filesFollow one taskContinuity without duplicate state
A new session should be able to find the authorized task, its acceptance criteria, current evidence and next action without reconstructing a conversation. In MDAAI 2.0, Project Elaboration owns scope and sequence; TASKS.json owns task state. Keeping each fact with one owner avoids conflicting status checkboxes, parallel registries and repeated work.
How the files work togetherWhat adoption adds—and does not add
The MDAAI 2.0 template family supplies a root AGENTS.md, five governance documents, project-owned Project Elaboration and a fresh TASKS.json. For any agent system, point its entry instructions to the nearest AGENTS.md. Applicable parent and scoped governance files are cumulative. Adoption is an explicitly authorized, project-by-project merge and migration, not a universal installer. The source package’s research code, dashboards, studies and existing task history are not copied into every adopted repository.
Exact 2.0 adoption boundaryTwo initial template families
The first-generation template uses an elaborated project plan, Work Orders, a work-order registry, corrective records and architecture decisions. MDAAI 2.0 concentrates routine work in one task registry and adds separate records only when they carry necessary context. A migration reconciles contradictory instructions and preserves completed history; it does not layer another active template over unreconciled rules. These are concrete template families implementing MDAAI, not the whole protocol. Template versions and protocol identities are distinct.
First-generation templateMDAAI 2.0 templateProtocol, templates and execution
MDAAI defines the governance method. Versioned templates supply project files that apply it. Your selected agents, coding harnesses and execution tools read those files and perform authorized work. Permissions, tests and runtime checks belong to those separate execution layers; choosing a template does not install or activate them.
Instructions are not automatic enforcement
Markdown instructions guide agent behavior. Structural validators can check fields, references and consistency; they cannot establish that a claim is true, grant authorization or prove a product works. Actual tests and relevant runtime observation support acceptance. Automated revision/publication software is a separate implementation with separate approvals—not a consequence of reading AGENTS.md.
Having difficulty reading? Watch the 91-second overview.
Narration and captions offer another way to explore the two template families.
English narration and captions · 1080 × 1080 · 1 min 31.3 sec. Download captions (SRT).
PROTOCOL → PRACTICE → PROGRESS
A stable protocol. Templates that evolve.
The protocol governs how work is authorized, reviewed and evidenced. A template gives that method a concrete home in project files. Improve those files through reviewed work; adopt a new version explicitly. The protocol can itself be revised through its own authorized process.
- 01Stable protocol
- 02Choose and configure a template
- 03Project governance files
- 04Review and improve
- 05Versioned template
- 06Explicit adoption
Review may be manual or agent-assisted. Publication does not activate a template or update your project.
Choose a templateSource references
Based on original contracts and templates. These are source locations, not installed-file claims. No private source archives are served.
MDAAI 2.0: AGENTS.mdMDAAI 2.0: docs/ADOPTION.mdMDAAI 2.0: scripts/validate.pyMDAAI 2.0: PROJECT-INTERNAL/GOVERNANCE/AUTHORITY.mdMDAAI 2.0: PROJECT-INTERNAL/GOVERNANCE/ENGINEERING.mdMDAAI 2.0: PROJECT-INTERNAL/GOVERNANCE/EVIDENCE.mdMDAAI 2.0: PROJECT-INTERNAL/GOVERNANCE/REASONING.mdMDAAI 2.0: PROJECT-INTERNAL/GOVERNANCE/RECORDS.mdAGENTS.mdMDAAI 2.0: PROJECT-INTERNAL/MANAGEMENT/PROJECT-ELABORATION.mdMDAAI 2.0: PROJECT-INTERNAL/MANAGEMENT/TASKS.json