One ADR file per closed decision

Platform spec ADR

One ADR file per closed decision

Back to Specification authority and embedded decisions ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• No directly attached article pages for this node.

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 0 SpecSection(s) · 7 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	no	no
implementation-anchors	no	no

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Specification authority and embedded decisions

  Parent feature hub

Context

Monolithic decisions-record articles and hub prose duplicated the same choices without a stable identifier or reader ADRs tab.

Decision

Each Standard feature must publish closed choices under adr/ as one file per decision (specLevel: adr, stable adrId, adrStatus, adrDate). Body must include ## Context, ## Decision, ## Consequences; add ## Verification anchors when testable. Legacy decisions-record.mdx and hub ## Decisions summaries remain valid during migration; new work must use adr/. Inception cross-cutting ADRs stay under Project inception.

Consequences

Superseded ADRs set supersedesAdr or link replacements in Consequences with a Git revision note. Hub ## Decisions summarizes by adrId only—no full ADR prose duplication.

Verification anchors

checkAdrSections and checkStandardFeatureDecisions in packages/trudoc/src/verify/platform-spec-content.ts.