Format Overview

StratMD files are standard Markdown with a small set of conventions to ensure consistency and parseability.

Core Structure

Every StratMD file includes:

• Optional H1 title
• Required YAML frontmatter (delimited by ---)
• Standardized H2 (##) sections
• Tables for all structured data
• Optional Mermaid code blocks for diagrams
• Wiki-style links for relationships ([[filename.strat.md]] or [[filename.strat.md#Section]])

Document Types & Naming Conventions

StratMD defines five primary document types:

• Foundation — foundation.strat.md Timeless identity (mission, values, beliefs, principles).
• Strategy — [name].strategy.strat.md Major strategic directions with goals, risks, and approach.
• Initiative — [name].initiative.strat.md Execution plans, projects, or tactical efforts.
• Insight — YYYY-MM-DD-[title].insight.strat.md Key learnings, observations, or research findings.
• Metrics — [scope].metrics.strat.md KPI dashboards and performance tracking.

Required Frontmatter (All Types)

type: foundation | strategy | initiative | insight | metrics
version: 0.1
schema: stratmd
status: draft | active | archived
owner: Name or Team
created: YYYY-MM-DD
last_updated: YYYY-MM-DD

Common Sections Across Types

Most types share optional but recommended sections:

• Context
• Key Assumptions (table)
• Strategic Constraints (bullets or table)
• Dependencies (table)
• Foundation Alignment (table)
• Success Criteria
• Relationships (table)
• Decision Graveyard (table - for negative knowledge)
• Changelog (table - required)

Type-specific sections are detailed in their respective pages:

• Foundation Format
• Strategy Format
• Other Formats (Initiative, Insight, Metrics)

Agent Parsing Notes

For AI agents:

• Load frontmatter first as the trust anchor
• Convert tables to JSON arrays
• Use Constraints and Decision Graveyard to avoid drift/repeats
• Follow links for hierarchical context

This overview provides the shared foundation—dive into type-specific pages for full templates.