31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Micro mode compresses artifacts but preserves critical gates
|
|
|
|
SM Flow SHALL allow `micro` mode to reduce artifact weight without skipping critical gates.
|
|
|
|
#### Scenario: Micro mode starts
|
|
|
|
- **WHEN** a change is classified as `micro`
|
|
- **THEN** the flow may merge or simplify devflow artifacts
|
|
- **AND** it SHALL still perform Phase 0.5 minimum context harvest, Phase 2 minimum clarification, Phase 2.9 commit gate, and Phase 4 lightweight backfill
|
|
|
|
#### Scenario: Micro mode is treated as skip permission
|
|
|
|
- **WHEN** the agent attempts to skip a critical gate because the change is small or low-risk
|
|
- **THEN** the flow SHALL treat that as a protocol deviation rather than a valid micro-mode optimization
|
|
|
|
### Requirement: Devflow updates happen during the flow
|
|
|
|
SM Flow SHALL update devflow artifacts during the relevant phases rather than deferring all updates to Phase 4.
|
|
|
|
#### Scenario: Phase-local information is produced
|
|
|
|
- **WHEN** a phase produces entry summary, evidence, decisions, architecture findings, or commit-gate conclusions
|
|
- **THEN** the corresponding devflow artifact is updated in or near that phase
|
|
|
|
#### Scenario: Phase 4 begins
|
|
|
|
- **WHEN** the flow enters Phase 4
|
|
- **THEN** devflow backfill is primarily a consolidation step rather than the first time those records are written
|