Crate-to-spec anchor map is canonical index
Platform spec ADR
Crate-to-spec anchor map is canonical index
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”Crate references were scattered across hubs without a single ownership surface.
Decision
Section titled “Decision”This feature hub is the canonical map from compiler/crates/* to platform-spec features; other pages link here instead of duplicating tables.
Consequences
Section titled “Consequences”New crates require anchor rows before Standard promotion of dependent features.
Verification anchors
Section titled “Verification anchors”- Implementation-map articles and
compiler/Cargo.tomlworkspace layout.