Overview

This section provides templates for creating content across the documentation site. Each template page describes when to use it, which site section it targets, and includes the full template as a copyable code block.

General Templates

Templates for common document types used across multiple site sections.

Template	Target Section	Use When
Architecture Decision Record	decisions/	Recording a technology or design decision
User Story	product/	Defining a feature requirement in story format
User Persona	product/personas/	Creating a new user persona profile
Behavior Description	product/use-cases/ or domain/	Documenting use cases and scenarios
Threat Model	process/	Performing STRIDE-based threat analysis
Security Audit Report	process/	Recording a security review
Operational Runbook	process/ or technology/	Writing step-by-step operational procedures

Project Decomposition Templates

Templates for multi-run project plans produced by the Project Decomposition workflow.

Template	Use When
Team Split Assessment	Documenting the complexity analysis and split recommendation
Project Plan (Run)	Defining entry/exit criteria, tasks, and handoffs for a single run
Choreography	Describing the execution sequence and artifact dependencies across runs

Authoring Templates

Structural templates for creating pages and sections on this site.

Template	Target Section	Use When
Content Page	Any section	Creating a new content page
Section Index	Any section	Creating a section landing page (index.md)

Backend Service Templates

Templates for specifying Kotlin backend service implementations in the operations repository.

Template	Use When
Task Specification	Defining a scoped implementation task with acceptance criteria
Incremental Service Requirements	Modifying an existing service (entities, methods, persistence, API)
Feature Requirements List	Specifying a new feature with domain modeling and requirements
New Service Implementation	Building a new service module from scratch

Frontmatter Reference

Every page on this site uses YAML frontmatter validated against the content schema. The minimum required fields are:

---
title: "Overview"
tags: [keyword1, keyword2]           # Recommended
domain: product                      # Recommended — one of: product, domain, system, vision,
                                     #   roadmap, process, technology, legal, decisions, about
maturity: draft                      # draft | review | published (default: published)
---

Additional optional fields: author, description, lastVerified, source, supersedes, comments.