Sibling articles under this feature previously restated requirements in inconsistent forms.
Resolver contract
Platform spec feature
Resolver contract
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Resolver 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/semantic-pipeline/resolver-contract/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Resolver 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_analysis/src/resolve/resolver.rscompiler/crates/beskid_analysis/src/resolve/items.rscompiler/crates/beskid_tests/src/analysis/resolve.rs
-
This feature hub defines the normative contract for **resolver contract** and links newcomer-oriented reference articles
Context
This feature hub defines the normative contract for resolver contract and links newcomer-oriented reference articles.
Decision
The reference compiler must implement Resolver 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_analysis/src/resolve/resolver.rscompiler/crates/beskid_analysis/src/resolve/items.rscompiler/crates/beskid_tests/src/analysis/resolve.rs
- Resolver contract - Contracts and edge cases States the normative guarantees and what happens at boundaries or failure edges.
- Resolver contract - Design model Explains the persistent concepts, entities, and boundaries this feature relies on.
- Resolver contract - Examples Gives concrete newcomer-friendly scenarios mapped to real compiler paths.
- Resolver contract - FAQ and troubleshooting Answers common operator and contributor questions with practical next checks.
- Resolver contract - Flow and algorithm Walks through runtime/order-of-operations behavior in the implementation.
- Resolver 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 resolver contract and links newcomer-oriented reference articles.
Implementation anchors
Section titled “Implementation anchors”compiler/crates/beskid_analysis/src/resolve/resolver.rsowns name resolution and scope lookup.compiler/crates/beskid_analysis/src/resolve/items.rsresolves item-level references.compiler/crates/beskid_tests/src/analysis/resolve.rsexercises resolver behavior in tests.
Decisions
Section titled “Decisions”No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-SEM-0004 … D-COMP-SEM-0006); use the reader ADRs tab for expandable detail.