sechmachine/labtimesheet
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: align repair branch coordination authority

Browse Source
This commit is contained in:
sechmachine
2026-08-15 14:41:48 +07:00
parent 97e991317d
commit 9802d5d17f
5 changed files with 22 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/plans/2026-08-15-access-navigation-icon-intern-picker.md
+10 -7
View File
@@ -9,20 +9,23 @@ feature-branch ownership areas.
## Implementation steps
1. Prove RED: the contributor guides lack the realizable repair-branch name.
2. Add one branch rule everywhere contributors, coordinators, and requirement
reviewers rely on it: `work/fix/<feature>/<what-fix>` from verified `main`.
2. Add one branch rule to contributor guides, design records, plans, and tracked
coordination authority: `work/fix/<feature>/<what-fix>` from verified
`main`.
3. State why `work/<feature>/fix/<what-fix>` is invalid while its persistent
`work/<feature>` ref exists.
4. Regenerate the local SRS after amending the existing operational requirement;
do not add a requirement ID or a use case.
5. Prove GREEN with the executable six-guide regression, requirement/use-case
counts, local-link resolution, and an immutable base-to-candidate whitespace
check. Commit the tracked guidance locally; do not push or merge.
5. Prove GREEN with the executable six-guide regression that independently
rejects a positive nested-form recommendation in every guide,
coordination-authority consistency, requirement/use-case counts, local-link
resolution, and an immutable base-to-candidate whitespace check. Commit the
tracked guidance locally; do not push or merge.
## Exit criteria
- The tracked guides, design record, implementation plan, and evidence record
agree on the same repair-branch spelling.
- The tracked guides, design record, implementation plan, root coordination
authority, and evidence record agree on the same repair-branch spelling.
- The local authoritative, explained, simple, and generated SRS catalogues keep
exactly 260 unique requirement IDs and the SRS keeps 14 use cases.
- The forbidden nested form is documented only as forbidden, not as a usable
docs/superpowers/specs/2026-08-15-access-navigation-icon-intern-picker-design.md
+5 -3
View File
@@ -33,6 +33,8 @@ push or merge without separate authority.
## Validation
The executable documentation validator checks the exact approved statement in
each tracked guide and rejects an injected positive nested-branch recommendation.
The evidence record also verifies requirement counts, generated SRS use-case
count, and local Markdown links.
each of the six tracked guides and independently rejects an injected positive
nested-branch recommendation in every guide. The copied root coordination
authority uses the same rule and is checked separately for consistency. The
evidence record also verifies requirement counts, generated SRS use-case count,
and local Markdown links.