Status: Active Layer: Non-normative scope guide
This document is a plain-language guide to keep the spec set lean and clear.
It does not define runtime, orchestration, or product behavior. Normative requirements belong only in their owning spec documents.
When deciding whether something belongs in the active spec set, prefer work that directly improves:
- product clarity
- user experience
- execution safety
- recovery and resumability
If a requirement does not materially help one of these, it is usually optional or out of scope.
- Use plain names and plain language.
- Avoid adding process-heavy requirements to core behavior.
- Avoid adding concepts that only serve one edge case.
- Prefer extending existing models over adding new control paths.
- Keep operator-facing behavior concrete and actionable.
Walkthroughs are a manual team practice.
They are not a built-in system requirement, runtime contract, or required structured artifact unless an owning spec explicitly adds that requirement later.
Before adding a new requirement, ask:
- Does this make the product or UX clearer for real users?
- Does this reduce real operational risk?
- Is this necessary now, or can it stay out of scope?
If the answer is unclear, keep the requirement out of the core spec.