Minimum article payload by role

Platform spec ADR

Minimum article payload by role

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
  Domain, Area and Feature template bundle

  Parent feature hub

Context

Article filenames implied depth (for example verification-and-traceability) while content remained TBD stubs.

Decision

Each bundle article must meet role minimums: design-model (model, invariants, diagram/table); contracts (testable MUST/SHOULD rules); verification (concrete test paths, not TBD); operations/migration (procedures); decisions-record (legacy—migrate to adr/); adr (one decision per file with SpecAdrChrome). Every article must include purpose, canonical references, detailed behavior, verification notes, and related topics. Feature hubs must publish a stable newcomer reading order (area → hub → conceptual articles → verification).

Consequences

ARTICLE_ROLE_THRESHOLDS in platform-spec-content.ts enforce section and line counts.

Verification anchors

packages/trudoc/src/verify/platform-spec-content.ts role thresholds.