MDAAIProtocol documentation
TEMPLATESGH

Templates

Choose a template to apply the MDAAI protocol. Configure its governance files for your project; agents and execution tools are separate layers.

By Eris Margeta Kurdali · Repository

Browse templates

2 templates

1.0.1 · Apache-2.0

MDAAI 1.0 — first-generation family

Work Orders, lifecycle protocols, checkpoints, schemas and blank project scaffolds.

Review before adoption

Inspect 91 files and source details
Template version
1.0.1
Historical source label
Independent named template MDAAI 1.0; standalone protocol separately versioned; constitution internal revision 1.8
Canonical source
Eris-Margeta/mdaai-template-1 @ 3263e95a30dee5c1699568f9f5bf8e493208d3b1
License
Apache-2.0 — retain inherited notices; see license scopes below.
Adoption status
Review before adoption · complete: false

2.0.1 · Apache-2.0

MDAAI 2.0

Six-file operating contract, fresh task registry and uninitialized project scope.

Review before adoption

Inspect 18 files and source details
Template version
2.0.1
Historical source label
Independent named template MDAAI 2.0; standalone protocol separately versioned
Canonical source
Eris-Margeta/mdaai-template-2 @ 3ae05fb46d92caf93d4ba63f6ddc6b95c04d6ea0
License
Apache-2.0 — retain inherited notices; see license scopes below.
Adoption status
Review before adoption · complete: false

Have a template to contribute?

Propose a listing through a pull request to the GitHub index. Review is required before a template is featured.

Submit a templateCatalog pull requests
Catalog pin, provenance and license scopes

Reviewed catalog commit 42f98556ce96c1c74abbd272fffe5524e463f96a · 109 files

Files are linked to the pinned public repository. This build does not include local source downloads.

Export provenance · License scopes · Known source link gaps

Versions and export boundaries

MDAAI protocol release 1.0.0 is independent of the named templates MDAAI 1.0 (release 1.0.1) and MDAAI 2.0 (release 2.0.1). Catalog 0.1.1, schema 1, imports immutable public package revisions through the same reviewed admission path as community templates: 91 and 18 verified literal payloads. The first template constitution internal revision is 1.8; historical document labels are origin metadata, not protocol releases. MDAAI 2.0 supplies six portable core files and project-owned Elaboration and TASKS.json scaffolds. Review and configure either package before adoption. Imported previews and downloads are read-only derivatives, not editable template authority.

Review before adoption

Both bundles are marked review-before-adoption and complete: false. All 105 listed files are exported; this status describes uninitialized downstream scaffolds, adoption review and known literal link gaps, not missing export files. First-generation references to PROJECT-DEVELOPMENT-ELABORATION.md and GUIDES/CHECKPOINT-PROTOCOL.md need reconciliation with the supplied owners. Review the export manifest, license scopes and known link-gap inventory. Back up the target, choose one active governance template configuration, reconcile existing rules, fill project identity and actual commands, then exercise a real task and resumption. No installer, automatic activation or guaranteed self-improvement is provided.

Improve, version, then adopt

Project experience can inform template improvements, manually or with agent assistance under the applicable protocol. Review the change and its evidence, publish a versioned template, then explicitly decide whether and how each project adopts it. A stable protocol governs this loop and may itself be revised through authorized review.

Source references

Based on original contracts and templates. These are source locations, not installed-file claims. No private source archives are served.

  • Public template catalog: templates.json

Search documentation

Search runs locally. No query leaves your browser.

↑ ↓ move · Enter open · Esc close