Mandatory Punnaraj Template Standard¶
Effective 2026-08-31, the Punnaraj template registry is an authorized system standard.
Master template¶
punnaraj-knowledge-dev/punnaraj-repository-template version 0.2 is the canonical master template and is mandatory as the default baseline whenever no more-specific mandatory template applies.
Specialized mandatory templates¶
| Template | Version | Required scope |
|---|---|---|
punnaraj-knowledge-dev/mkdocs-template |
0.1.0 |
MkDocs documentation or static-site publication |
punnaraj-knowledge-dev/punnaraj-docs-template |
0.1.0 |
canonical document control, registry, publication evidence, long-lived records |
punnaraj/workflows-starter-template |
0.1.0 |
Cloudflare Workflows / durable multi-step workflow runtime |
punnaraj/mcp-cloudflare-template |
0.5.0 |
Cloudflare-hosted MCP / bounded Cloudflare observer runtime |
Specialized templates inherit the document-control contract from the master template.
Mandatory document completion rule¶
A work product is not finished when required metadata is missing or invalid. This includes requirement, design, implementation plan, implementation record, verification evidence, operational record, announcement, and other governed documents.
Documents must remain Obsidian-compatible Markdown where Markdown is the canonical form, preserve provenance and lineage, and use explicit identity/version/status metadata.
Selection rule¶
- Start from the master template by default.
- When a specialized template's declared scope applies, use that template.
- Specialized templates do not waive the master's metadata, provenance, lifecycle, or completion requirements.
- Historical or superseded templates are reference/library material only unless explicitly re-authorized.
Authority¶
This standard is authorized by the human root authority. The operator is responsible for applying, maintaining, verifying, and reporting the standard across governed work.