Feature hub authority
Platform spec ADR
Feature hub authority
Spec standingStandard
- Contracts and edge cases Normative guarantees and known edge cases for `Crate-to-spec anchors`.
- Design model Conceptual model for `Crate-to-spec anchors` and its subsystem boundaries.
- Examples Practical examples that demonstrate `Crate-to-spec anchors` behavior.
- FAQ and troubleshooting Common questions and debugging guidance for `Crate-to-spec anchors`.
- Flow and algorithm End-to-end control flow and major algorithmic steps for `Crate-to-spec anchors`.
- Verification and traceability How `Crate-to-spec anchors` requirements map to tests and implementation anchors.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”Sibling articles under this feature previously restated requirements in inconsistent forms.
Decision
Section titled “Decision”This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Section titled “Consequences”Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
Section titled “Verification anchors”site/website/src/content/docs/platform-spec/compiler/implementation-map/crate-to-spec-anchors/index.mdxarticle bundle under the same feature directory.