tmk241/mim
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify redgate requirement governance

Browse Source
This commit is contained in:
slhx agent
2026-06-21 19:53:46 +02:00
parent 70d8582448
commit b83431aefc
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+1 -1
View File
@@ -3,7 +3,7 @@
## Authority ## Authority
- `PRODUCT.md` is the durable product orientation and product boundary for `mim`. - `PRODUCT.md` is the durable product orientation and product boundary for `mim`.
- `REQUIREMENTS.md` is the checkable requirement authority. Cite rows as `req: component/id` in future code, tests, and design notes when a change implements or protects that requirement. - `REQUIREMENTS.md` is the checkable requirement authority. Cite rows as `req: component/id` in future code, tests, and design notes when a change implements or protects that requirement. If implementation work changes durable product obligations, acceptance, safety/recovery behavior, or verification duties, update `REQUIREMENTS.md` in the same slice or explicitly report `REQUIREMENT IMPACT: none` with the reason.
- User instructions for the current task override these files when they conflict. - User instructions for the current task override these files when they conflict.
## Product constraints ## Product constraints
REQUIREMENTS.md
+2
View File
@@ -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] 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 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 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 ## governance