Required Domain Area and Feature hub sections

Platform spec ADR

Required Domain Area and Feature hub sections

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

Inconsistent hub shapes made navigation and CI layout validation unpredictable.

Decision

Domain pages must include eight ordered sections (scope, terminology, principles, area map, guarantees, conformance, change policy, related domains). Area pages must include eight area sections (contract, boundaries, internal model, feature index, failure model, verification matrix, operations, related areas). Feature hubs must include eleven sections ending with Decisions plus adr/ (contract, I/O, state, algorithms, edge cases, compatibility, security/performance, examples, verification, related features, decisions).

Consequences

layout.json presets align with SpecSection ids; articles must not redefine hub-only canonical requirements.

Verification anchors

verify:platform-spec-layout; feature-contract-default preset.