Template Export

Maestro-Prime is intended to become the governing parent baseline for future projects.

That means export is a controlled release process, not a copy-paste exercise.

Template Export Should Preserve

• docs topology
• governance schema
• sync and validation scripts
• semantic registry model
• deployment profile and manifest model
• learning-plane model
• skills, commands, and workflows

Template Export Should Remove Or Parameterize

• product-specific names
• environment-specific values
• secrets and runtime credentials
• one-off examples that do not generalize

Canonical Sources

The governed source artifacts for this page live in the repository under:

• docs/runbooks/template-repo-export-and-release.md
• docs/standards/maestro-prime-inheritance-standard.md
• template/agent-prompts.manifest.json
• template/export.manifest.json
• template/inheritance-policy.json
• template/inheritance-state.json
• template/release.version.json
• template/template.config.json