2026-06-01T10:53:12Z - 2026-09-01T10:53:12Z
Overview
21 Issues closed from 1 user
Closed
#16 doc-claims is red in every freshly scaffolded project, and the design says it should be
Closed
#22 doc-triggers cannot see root documents, so their headers are decorative
Closed
#20 doc-triggers matches the glob but not the trigger's verb, so the trust map fires on everything
Closed
#21 doc-triggers never fires three documents whose Governs carries a gloss after the glob
Closed
#17 doc-triggers.py resolves the repo root by depth, so it climbs out of every project that adopts it
Closed
#18 prove-guard.sh reads only one order of failure summary, so node --test falls through to a count that false-fires exit 3
Closed
#19 prove-guard.sh refuses with exit 1, not the documented 2, so a mistyped find-string accuses the guard of being broken
Closed
#15 scaffold.sh leaves every new project with a broken link and a red doc-claims
Closed
#13 README.md says twenty scripts and the directory holds twenty-three
Closed
#12 preflight.sh calls a duplicated header present when only the first one counts
Closed
#9 preflight.sh — the live-URL checks nobody runs
Closed
#10 controls.sh — no way to answer which controls a project actually has
Closed
#11 secrets.sh prints the credential it found
Closed
#7 restore-check.sh — nothing has ever restored a backup
Closed
#8 secrets.sh --built — the scan stops at the repository, and secrets ship in the bundle
Closed
#6 docs/OPERATIONS.md — there is no runbook, and no document says what watches production
Closed
#1 Mark applicability and provenance on entries that do not apply everywhere
Closed
#5 SECURITY.md says nothing about trust boundaries, user-held credentials, or transcripts
Closed
#4 Ten standing security checks the checklist does not have
Closed
#2 Add QA pass H — authorization and abuse
Closed
#3 Add QA pass I — money flowing backwards (only where money moves)
1 Issue created by 1 user
Opened
#14 The Template cannot be mapped on the Command Center: it has no branding