045-command-surface-release-layer
The command surface in the release family (amends 031)
A narrow amendment of approved spec 031 (itself amending spec 021). Spec 027 adds `rustev-surface`, the pure command renderer every host calls, and requires the CLI to call it instead of its own copy. The CLI is a published release member, so its new dependency must be published first, in a crate layer of its own: 031 3.1's layer table has no slot between `rustev-eval` and the CLI. This spec adds `rustev-surface` to the release family, states the crate layers as the topological levels the release policy already computes from `cargo metadata`, admits a crate that a release member depends on once the crate exists and passes its checks, and keeps the release-set test's member list as the deliberate, reviewed record of membership. Ratified by the owner on 2026-10-20 (A-42).
Read the full pinned specification ↗Relationships
Claimed units
- extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Makefile" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "directory", "path": "scripts/acceptance/" } }
Source headings
- 045: The command surface in the release family (amends 031)
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 Membership
- 3.2 Crate layers
- 4. Out of scope
- 5. Observable negative cases
- Acceptance
- Verification
- Implementation record
Frozen anchors
No frozen anchors declared.