Feature hub authority

Platform spec ADR

Feature hub authority

Back to Rules and diagnostics catalog ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Contracts and edge cases Rule-level guarantees and high-risk semantic edge cases. article Standard
• Design model Mental model for staged semantic rules and diagnostic production. article Standard
• Examples Practical examples of semantic rule outcomes and diagnostic generation. article Standard
• FAQ and troubleshooting Common semantic-pipeline debugging questions and practical checks. article Standard
• Flow and algorithm End-to-end semantic rule flow from resolved items to user-facing diagnostics. article Standard
• Verification and traceability How semantic rule behavior is validated and traced to source modules. article Standard

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) · 5 H2 heading(s)

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

Related spec docs

• Feature
  Rules and diagnostics catalog

  Parent feature hub

Context

Sibling articles under this feature previously restated requirements in inconsistent forms.

Decision

This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.

Consequences

Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.

Verification anchors

• site/website/src/content/docs/platform-spec/compiler/semantic-pipeline/rules-and-diagnostics-catalog/index.mdx
• article bundle under the same feature directory.