Sibling articles under this feature previously restated requirements in inconsistent forms.
Registry and overrides contract
Platform spec feature
Registry and overrides contract
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Registry and overrides contract.
Context
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/resolution-and-projects/registry-and-overrides-contract/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Registry and overrides contract.
Context
Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
compiler/crates/beskid_tests/src/projects/corelib/mod.rscompiler/crates/beskid_cli/src/commands/
-
This feature hub defines the normative contract for **registry and overrides contract** and links newcomer-oriented refe
Context
This feature hub defines the normative contract for registry and overrides contract and links newcomer-oriented reference articles.
Decision
The reference compiler must implement Registry and overrides contract as documented in this feature hub and its article bundle.
Consequences
Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
compiler/crates/beskid_tests/src/projects/corelib/mod.rscompiler/crates/beskid_cli/src/commands/
- 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).
This feature hub defines the normative contract for registry and overrides contract and links newcomer-oriented reference articles.
Implementation anchors
Section titled “Implementation anchors”compiler/crates/beskid_tests/src/projects/corelib/mod.rsvalidates project source selection behavior.compiler/crates/beskid_cli/src/commands/provides CLI-level switches for registry interaction.pckg/src/Server/is the registry-side system consumed by compiler/project tooling.
Decisions
Section titled “Decisions”No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-PROJ-0007 … D-COMP-PROJ-0009); use the reader ADRs tab for expandable detail.