Skip to Content
EngineeringDecisions (ADRs)Decision log

Decision log

Ten architecture decision records, numbered in writing order. Each has the five headings Context, Decision, Consequences, Alternatives considered and Follow-ups, and an <AdrMeta> block with status, date and deciders. A record is never edited into a different decision: a new record supersedes it, the old one is marked Superseded and its body stays. The canonical Markdown lives in decisions/ at the workspace root; these pages mirror it. Three passages that spell the kit’s internal direction name (0001 Context, 0002 Context and Decision, the 0007 title) are reworded here because check-brand rejects the phrase; everything else is verbatim.

ADRTitleStatusDate
0001Adopt the product-forge method and the reference profileAccepted2026-09-13
0002Single brand, product taxonomy, pillars, stages and prefix ruleAccepted2026-09-13
0003Program as the tenant scope and the 72-permission catalogAccepted2026-09-13
0004Assertion kinds and origin on every finding, hypothesis and proposed stepAccepted2026-09-13
0005Identity model with a local development identity modeAccepted2026-09-13
0006Enumerations as text columns with named CHECK constraintsAccepted2026-09-13
0007Theme tokens from the brand kit, monochrome product accents, 4/8 px geometryAccepted2026-09-13
0008Research-agent action protocol (no git actions)Accepted2026-09-13
0009Documentation structureAccepted2026-09-13
0010Repository layout, local repositories without remotes, release deferredAccepted2026-09-13

What earns a record

One significant decision: a hosting or identity choice, a data-model rule, a taxonomy change, a navigation model, a positioning change, or a change to the build method itself (a new gate, a new release rule). Not a bug fix and not a feature. New records take the next number, are added to _meta.ts in numeric order, and get a row in this table with the count in the intro bumped.