Clarify redgate requirement governance
This commit is contained in:
@@ -45,6 +45,8 @@ Rows are redgate TSV requirements: `ring<TAB>id<TAB>summary [tag]`.
|
||||
0 002 Every product slice SHALL include adversarial carry-their-weight verification for realistic failure, boundary, or regression cases. [test]
|
||||
1 003 Protocol, headless session, replay, and fixture tests SHALL be preferred over brittle UI snapshots unless rendering behavior is the claim. [test]
|
||||
1 004 Test/support code SHALL not introduce runtime config, plugin, installer, telemetry, or product surfaces. [test]
|
||||
1 005 Terminal-visible behavior changes SHALL be verified by the terminal E2E matrix or by an explicitly narrower rendered-terminal proof. [test]
|
||||
1 006 Generated E2E evidence artifacts SHALL stay under ignored build output and SHALL not dirty a clean source tree. [test]
|
||||
|
||||
## governance
|
||||
|
||||
|
||||
Reference in New Issue
Block a user