37 lines
1.5 KiB
Markdown
37 lines
1.5 KiB
Markdown
# sm-flow Standard Change Spec
|
|
|
|
## ADDED Requirements
|
|
|
|
### Requirement: Standard Change Has Full OpenSpec Artifacts
|
|
|
|
A standard `sm-flow` change SHALL have `proposal.md`, independent `design.md`, `specs/`, and `tasks.md`.
|
|
|
|
#### Scenario: Standard fixture is committed
|
|
|
|
- **Given** a change is classified as `standard`
|
|
- **When** commit validation runs
|
|
- **Then** `proposal.md`, `design.md`, at least one spec file, and `tasks.md` exist
|
|
- **And** the artifacts are aligned from proposal to design to specs to tasks
|
|
|
|
### Requirement: Standard Archive Has Evidence
|
|
|
|
A standard `sm-flow` archive SHALL include `brief.md`, `evidence.md`, `decisions.md`, and `acceptance.md` in devflow.
|
|
|
|
#### Scenario: Standard fixture is archived or accepted
|
|
|
|
- **Given** a standard validation change has completed apply checks
|
|
- **When** devflow records are written
|
|
- **Then** `evidence.md` exists as a separate file
|
|
- **And** it records the static and script validation evidence used for acceptance
|
|
|
|
### Requirement: Scale Definitions Remain Centralized
|
|
|
|
Standard-specific artifact requirements SHALL be defined by `references/scales.md`; other files may reference those requirements but not carry a competing full definition.
|
|
|
|
#### Scenario: Standard wording is scanned
|
|
|
|
- **Given** sm-flow references mention standard behavior
|
|
- **When** scale definition phrases are scanned
|
|
- **Then** complete standard definitions appear only in `references/scales.md`
|
|
- **And** operational files defer to the current scale rather than hard-coding alternative standard rules
|