Domain

Documentation & Metadata

Owner documentation, product context, decision records, and machine-readable repository identity.

Architecture Documentation & Metadata

Catalog Descriptors

Machine-readable repository identity that tells catalog systems what a repository is and produces, and where the authoritative definitions live.

.descriptor/ 2

Architecture Documentation & Metadata

Code Map

A generated CODEMAP.md that says what each area of the repository is for and which local README to open next — a navigation guide, not a reference.

CODEMAP.md 2

Convention Documentation & Metadata

Decision Records

Architecture decision records are a last resort, written only when the repository’s structure, code, tests, and owner documentation cannot make a choice clear.

docs/pdlc/decisions/ 2

Lifecycle Documentation & Metadata

Issue Plan Tree

Plans live on disk as a tree of milestone folders and issue files that a planner reserves and syncs into Gitea, moving from slug-only drafts to ID-prefixed synced names.

<root>/ 1

Convention Documentation & Metadata

Managed Standard Files

Standard files copied into every repository carry a DO NOT EDIT header; they are changed at their source, never in the repository that received them.

./ 0

Convention Documentation & Metadata

Owner Documentation

Conventions are described beside the thing that owns them — a directory’s layout in its own README, a command’s behaviour in its module or script.

<area>/README.md 4

Architecture Documentation & Metadata

Product Development Life Cycle

docs/pdlc/ holds the durable product context behind a repository — problems, constraints, tradeoffs, and decisions — and nothing short-lived.

docs/pdlc/ 2

Convention Documentation & Metadata

Reference Over Duplication

Each fact is stated once, where it is maintained, and every other place that needs it points there instead of keeping a copy.

./ 2