Pure Beskid modules out of scope
Platform spec ADR
Pure Beskid modules out of scope
Spec standingStandard
- Contracts and edge cases Stability guarantees for runtime-backed corelib APIs.
- Design model Corelib APIs implemented by runtime builtins and ABI-stable syscall surfaces.
- Examples Examples of runtime-backed corelib surfaces.
- FAQ and troubleshooting FAQ for runtime-backed corelib surfaces.
- Flow and algorithm Call path from Beskid corelib methods to runtime builtins.
- Verification and traceability Verification for runtime-backed corelib surfaces.
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”Not every corelib module is runtime-backed.
Decision
Section titled “Decision”| Rule | Detail |
|---|---|
| In scope | Builtin/syscall facades documented here |
| Out of scope | Pure Beskid foundation modules |
Consequences
Section titled “Consequences”This feature does not duplicate language-meta semantics for pure libraries.
Verification anchors
Section titled “Verification anchors”foundation package compile tests.