Feature hub authority
Platform spec ADR
Feature hub authority
Spec standingStandard
- Registry and overrides contract - Contracts and edge cases States the normative guarantees and what happens at boundaries or failure edges.
- Registry and overrides contract - Design model Explains the persistent concepts, entities, and boundaries this feature relies on.
- Registry and overrides contract - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths.
- Registry and overrides contract - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks.
- Registry and overrides contract - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation.
- Registry and overrides contract - Verification and traceability Shows how the team proves this feature works and where evidence lives.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
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/resolution-and-projects/registry-and-overrides-contract/index.mdxarticle bundle under the same feature directory.