Standard feature hubs require adr directory

Platform spec ADR

Standard feature hubs require adr directory

Back to Domain, Area and Feature template bundle ◎ 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) · 11 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

  ADR governance

Context

Standard features shipped without traceable closed choices, blocking the reader ADRs tab.

Decision

Every Standard feature hub must include ## Decisions (open items or no open decisions plus adrId pointers) and publish at least one `adr/<slug>.mdx` with specLevel: adr unless explicitly exempt in a Standard maintenance policy. Each ADR must include Context, Decision, and Consequences. New decisions must not be added only to monolithic decision tables.

Consequences

Reference: Concurrency package ADRs. Legacy decisions-record.mdx is migration-only.

Verification anchors

PSC003 in platform-spec-content.ts.