Canonical corelib package identity
Platform spec ADR
Canonical corelib package identity
Spec standingStandard
- Contracts and edge cases Normative guarantees and known edge cases for `Corelib discovery and packaging`.
- Design model Conceptual model for `Corelib discovery and packaging` and its subsystem boundaries.
- Examples Practical examples that demonstrate `Corelib discovery and packaging` behavior.
- FAQ and troubleshooting Common questions and debugging guidance for `Corelib discovery and packaging`.
- Flow and algorithm End-to-end control flow for corelib discovery, materialization, and packaging.
- Verification and traceability How `Corelib discovery and packaging` 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”Registry, CLI, and analysis must agree on one package name.
Decision
Section titled “Decision”| Rule | Detail |
|---|---|
| Identity | Package name corelib; sources under beskid_corelib |
| Legacy | standard_library paths may alias; identity remains corelib |
Consequences
Section titled “Consequences”pckg publish, resolver, and docs use the same identity string.
Verification anchors
Section titled “Verification anchors”resolver.rs; beskid_tests corelib project fixtures.