Markdown-first platform-spec authoring

Platform spec ADR

Markdown-first platform-spec authoring

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

Heavy Astro component usage made diffs noisy and hid normative prose from content validators.

Decision

Every new or reworked topic must choose one canonical level: Domain, Area, or Feature. Regular sections must be markdown headings/lists/admonitions first. Architecture visuals must use fenced arch (Mermaid C4); procedural flows may use fenced mermaid. Inline graph components in docs are legacy-only. Generics in prose must use one backtick literal per type; Mermaid labels must not contain raw `<` or `>`.

Consequences

Component usage requires a rationale note; tables stay sparse.

Verification anchors

remark-arch-code-fence; layout minMarkdownHeadings where enabled.