12.4 Proposed vs Standard
Maturity labels—what you can cite in arguments and what is still forming.
Proposed vs Standard
Spec pages carry status metadata. Treat it like a fire rating on a door—not decoration.
status | Meaning |
|---|---|
| Proposed | Incomplete or unstable; do not cite as enforceable language law |
| Standard | Enforceable contract at this Git revision; needs decisions + verification anchors |
From Specification authority.
Standard gates
Section titled “Standard gates”A Standard feature hub must have:
- Normative MUST/SHOULD/MAY prose
- Verification anchors (tests, crates, registry links)
## Decisionson the hub and/oradr/per decision
Placeholder-only bundles or circular canon stubs must downgrade to Proposed until fixed (Feature hub template).
v0.x bands
Section titled “v0.x bands”Roadmap labels like v0.2 describe delivery scope, not alternate spec URLs—see Release and versioning policy.
For readers
Section titled “For readers”When building on Beskid for production, prefer Standard language-meta articles. When experimenting, read Proposed pages—but do not blame the compiler when the spec said “still forming.”