Templates

Choose files with a known origin

A template is a concrete implementation of the protocol in files. This reviewed catalog contains 84 first-generation files and 9 MDAAI 2.0 files. Required files belong to the selected contract; conditional files apply when their governing condition is met; optional files add compatibility or tooling. Selecting a role does not waive stronger project rules.

The literal file gallery

Inspect the pinned entry point and each file before use. Catalog 0.1.0, template version and protocol identity describe different things. Source references identify provenance; the public export can be read without access to the original source repositories.

Reviewed catalog commit 4ad670f9402e8699ed969ae719188196ef089aae · 93 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

The first-generation family carries VERSION 1.0.0 while AI-INSTRUCTIONS.md identifies Version 1.7; supporting protocols have their own labels. It is not a pristine original 1.0 release. MDAAI 2.0 supplies six portable core files, an optional CLAUDE.md pointer and fresh project-owned Elaboration and TASKS.json scaffolds. Its root contract omits laboratory-specific commands. Original source repositories remain unchanged.

Review before adoption

Both bundles are marked review-before-adoption and complete: false. All 93 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 profile, 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.