QA verdicts

Pass/fail, grouped by requirement. Computed from the qa:approved / qa:rejected labels on issues carrying a → **REQ-00N** marker — the same labels QA's own veto (scripts/qa-gate.sh, scripts/qa-verdict.sh) already enforces. Nobody is asked for a verdict; the label is the verdict.

14
requirements
18
approved
4
rejected
197
pending
REQStatusIssues
REQ-001 pending
  • pending #2 P0-1: DoD check — policy-as-code required status check
  • pending #18 P0-9: Generated tracker surfaces — project board sync + wiki publish
  • pending #22 P0-11: Project sync adds missing work items to the board
  • pending #25 P0-13: A session is judged on what it shipped, not its exit code
  • pending #38 P0-16: A closed work item carries a terminal status label
  • pending #129 BUG: a session that correctly finds nothing to change is marked a fail
  • approved #232 Dispatcher builds the agent prompt from the issue's current content, n
  • pending #251 The board sync has been failing for two days — 16 tickets never reache
  • pending #321 Agents can ask a human and hear the answer: questions, wake on reply,
REQ-002 pending
  • pending #3 P0-2: Dispatcher v0 — work item → headless agent session
  • pending #4 P0-3: Developer role pack v0
  • pending #9 P0-8: Orchestrator pack v0 — assignment loop
  • pending #29 P0-15: Dispatcher grants the permissions it compiled, and counts retri
  • pending #39 P1-1: Product Manager role pack v0
  • pending #42 P0-17: Per-role dispatch credentials — least privilege, not one omnibu
  • pending #49 P1-4: Architect role pack v0
  • pending #50 P1-5: Tech Writer role pack v0
  • pending #64 P1-9: Delivery Lead role pack — governance gets an owner
  • pending #124 Throughput and scope: raise WIP, give ceremonies an owner, settle REQ-
  • pending #184 The PRD names the eighth role twice, so the page reports 7/8 forever
  • pending #185 P1-19: status.py hardcodes a role list that has never matched the pack
  • pending #211 P4-5: A security role and an operations role — nothing has ever review
  • pending #223 Decision needed: accept ADR-0008 (security + operations roles) or revi
  • approved #233 compile-pack.py: write_scope never reaches the agent prompt, and --che
  • pending #320 Role-pack skills reach dispatched sessions, on demand (P0-1)
  • pending #322 One GitHub App replaces the three PATs; a required check enforces who
  • pending #332 Codex sessions get the role's skills too, on demand
REQ-003 pending
  • pending #3 P0-2: Dispatcher v0 — work item → headless agent session
  • pending #97 P0-18: Codex compiler target — compile_codex
  • approved #113 BUG: shipped-nothing gate fails open when a compiled pack has no produ
  • pending #210 P4-4: More harness targets — one works, the criteria claim two
  • pending #222 P4-7: Dispatch under a second harness — the compiler has two targets,
  • pending #241 P4-7 follow-up: run the live codex trial dispatch.yml now supports
  • pending #268 Two-repo dispatch: the product checkout's origin pointed at the contro
  • pending #269 Every claude-code session since 2026-09-08 21:47 UTC dies in under a s
  • pending #318 Developer pack: test, debug and slice before opening the PR (adapted f
  • pending #332 Codex sessions get the role's skills too, on demand
REQ-004 pending
  • pending #18 P0-9: Generated tracker surfaces — project board sync + wiki publish
  • pending #123 P3-4: Tracker adapter — GitHub and Jira behind one contract
  • pending #192 P3-7: Rewire sync-project.py through the tracker seam — it still calls
  • pending #202 P4-1: Declare the product registry — one place every product is define
  • pending #206 Build scripts/check-products.py against policies/products.yaml
  • pending #207 PILOT: one story, one product repo, issue to deployed, nothing untrack
  • pending #208 P4-2: Dispatcher targets a product repo, not only itself
  • pending #224 Register a second product and run one story against it — the two-repo
  • pending #251 The board sync has been failing for two days — 16 tickets never reache
  • pending #261 Wire check-products.py as a required status check on policies/products
  • approved #262 products.yaml: foundry-program and ai-sdlc-pilot share project board 2
  • pending #290 Work items carry their product, so the orchestrator and board sync rou
  • pending #323 foundry-init: one idempotent command from empty repo to first dispatch
  • pending #324 Owner and repo constants live in one config file, not ~20 files
  • pending #331 Interview me about foundry-trial
REQ-005 pending
  • pending #2 P0-1: DoD check — policy-as-code required status check
  • pending #6 P0-5: Traceability matrix generator v0
  • pending #50 P1-5: Tech Writer role pack v0
  • pending #100 BUG: approval-gate tests are path-filtered away from the files they as
  • pending #150 BUG: DoD reports trailers missing when they are present but outside th
  • pending #168 P1-17: Check at refinement that a story's criteria fit the assigned ro
  • pending #173 Define a DoD deferral form so honesty does not fail the build (policy
  • pending #174 check-test-wiring greps for strings, so discovered tests need a commen
  • pending #176 BUG: DoD counts checkbox-shaped sample input in code fences as unticke
  • pending #180 P1-18: Implement the DoD deferral form in dod-check and the dispatch p
  • pending #200 BUG: session-end aborts on an unbound variable — 43 of 74 assertions r
  • pending #209 P4-3: Bootstrap a product repo — and verify it, rather than trusting t
  • pending #219 BUG: a deferral that wraps across lines is rejected — the reason is on
  • pending #225 SECURITY: every required check runs the pull request's own code
  • pending #226 21 review findings on the foundational PRs were never read, answered,
  • pending #227 Every new product repo would start with the same unread-review hole
  • approved #231 dod-check.sh: trailer values, issue existence, and fork-PR reporting a
  • approved #235 Traceability matrix: squash-merge trailers, failed PR lookups, and a b
  • pending #246 CRITICAL: bootstrap requires a dod check the product repo cannot produ
  • pending #322 One GitHub App replaces the three PATs; a required check enforces who
REQ-006 pending
  • pending #7 P0-6: Standup digest v0 — event-derived, never self-reported
  • pending #9 P0-8: Orchestrator pack v0 — assignment loop
  • pending #39 P1-1: Product Manager role pack v0
  • pending #40 P1-2: Refinement trigger — dispatch the PM when the ready queue emptie
  • pending #51 P1-6: Retro ceremony v0 — event-derived, one issue per window
  • pending #114 P2-2: Declare all five ceremonies as policy
  • pending #115 P2-3: Planning, review and retro ceremony workflows
  • pending #124 Throughput and scope: raise WIP, give ceremonies an owner, settle REQ-
  • pending #140 P2-9: Ceremony declaration validator
  • pending #146 REQ-006 read 100% while two of five ceremonies could not run
  • pending #179 46 of 47 closed stories had no QA verdict — the veto is fine, the rule
REQ-007 rejected
  • pending #20 P0-10: One GitHub credential + correct setup steps
  • pending #23 P0-12: Budgets measure cost; sessions report what they did
  • pending #40 P1-2: Refinement trigger — dispatch the PM when the ready queue emptie
  • pending #45 P1-3: Approval gates as policy — critical work waits for a person
  • approved #52 P1-7: Enforce the approval-gate SLA
  • pending #59 P1-8: Document the approval gates and their SLA
  • pending #64 P1-9: Delivery Lead role pack — governance gets an owner
  • pending #101 Governance: narrow the delivery-lead write scope, and scope the approv
  • pending #104 P1-12: Decisions dashboard — what is waiting on a human, and what was
  • pending #129 BUG: a session that correctly finds nothing to change is marked a fail
  • pending #134 BUG: a by-design workflow-scope refusal is indistinguishable from a br
  • pending #173 Define a DoD deferral form so honesty does not fail the build (policy
  • pending #180 P1-18: Implement the DoD deferral form in dod-check and the dispatch p
  • pending #193 P3-8: Wire the sign-off gate into the loop — the client layer has neve
  • rejected #198 Exercise the sign-off gate live and record REQ-008's note (post-merge
  • pending #219 BUG: a deferral that wraps across lines is rejected — the reason is on
  • pending #225 SECURITY: every required check runs the pull request's own code
  • pending #321 Agents can ask a human and hear the answer: questions, wake on reply,
REQ-008 rejected
  • pending #116 P2-4: Client sign-off as policy-as-code
  • pending #117 P2-5: Client portal — what was delivered and what needs signing
  • pending #118 P2-6: Transcript to draft PRD and candidate requirements
  • pending #148 P2-10: Validators for the environment ladder and sign-off policies
  • pending #193 P3-8: Wire the sign-off gate into the loop — the client layer has neve
  • rejected #198 Exercise the sign-off gate live and record REQ-008's note (post-merge
  • pending #331 Interview me about foundry-trial
REQ-009 pending
  • pending #2 P0-1: DoD check — policy-as-code required status check
  • pending #5 P0-4: QA role pack v0 + verdict enforcement
  • pending #98 P0-19: QA verdict dashboard — pass/fail matrix by requirement
  • pending #179 46 of 47 closed stories had no QA verdict — the veto is fine, the rule
  • pending #223 Decision needed: accept ADR-0008 (security + operations roles) or revi
  • pending #226 21 review findings on the foundational PRs were never read, answered,
  • approved #231 dod-check.sh: trailer values, issue existence, and fork-PR reporting a
  • approved #234 qa-gate.sh treats a failed label lookup as an empty (non-rejected) lab
REQ-010 rejected
  • pending #53 P2-1: Environment ladder declared, production gate real
  • pending #121 P2-7: Environment ladder declared as policy
  • pending #122 P2-8: Deploy workflow with a real production gate
  • pending #148 P2-10: Validators for the environment ladder and sign-off policies
  • pending #183 Exercise the production gate once deploy.yml is on main
  • pending #184 The PRD names the eighth role twice, so the page reports 7/8 forever
  • rejected #191 P3-6: Promote the published site through the ladder — the only real de
  • pending #207 PILOT: one story, one product repo, issue to deployed, nothing untrack
  • approved #265 The daily dashboards deploy waits on the prod reviewer every day and i
  • pending #323 foundry-init: one idempotent command from empty repo to first dispatch
REQ-011 rejected
  • pending #6 P0-5: Traceability matrix generator v0
  • pending #7 P0-6: Standup digest v0 — event-derived, never self-reported
  • pending #18 P0-9: Generated tracker surfaces — project board sync + wiki publish
  • pending #22 P0-11: Project sync adds missing work items to the board
  • pending #27 P0-14: Programme status page — traced vs actually satisfied
  • pending #38 P0-16: A closed work item carries a terminal status label
  • pending #59 P1-8: Document the approval gates and their SLA
  • pending #96 P1-10: Burndown & velocity dashboard
  • pending #103 P1-11: Architecture decision records — establish the format and backfi
  • pending #104 P1-12: Decisions dashboard — what is waiting on a human, and what was
  • pending #105 P1-13: ADR dashboard — render the decision records as a page
  • pending #106 P1-14: Publish the decisions and ADR pages — dashboards workflow wirin
  • pending #117 P2-5: Client portal — what was delivered and what needs signing
  • pending #126 P1-15: ADR validator
  • pending #127 Three merges in a row conflicted on build.py's page registry
  • pending #142 BUG: main is red because a requirement was satisfied — status test pin
  • pending #146 REQ-006 read 100% while two of five ceremonies could not run
  • pending #159 Self-hosting verdict is hardcoded 'unproven' while the page prints 46
  • pending #164 P1-16: Compute the self-hosting verdict, and catch notes that contradi
  • pending #184 The PRD names the eighth role twice, so the page reports 7/8 forever
  • pending #185 P1-19: status.py hardcodes a role list that has never matched the pack
  • rejected #191 P3-6: Promote the published site through the ladder — the only real de
  • pending #203 Repo renamed to ai-sdlc — update live defaults, keep historical citati
  • approved #235 Traceability matrix: squash-merge trailers, failed PR lookups, and a b
  • pending #245 The published site silently stopped deploying three days ago
  • pending #251 The board sync has been failing for two days — 16 tickets never reache
  • approved #262 products.yaml: foundry-program and ai-sdlc-pilot share project board 2
  • approved #265 The daily dashboards deploy waits on the prod reviewer every day and i
  • pending #290 Work items carry their product, so the orchestrator and board sync rou
  • pending #324 Owner and repo constants live in one config file, not ~20 files
REQ-012 pending
  • pending #4 P0-3: Developer role pack v0
  • pending #8 P0-7: Budgets + escalation ladder v0
  • pending #20 P0-10: One GitHub credential + correct setup steps
  • pending #23 P0-12: Budgets measure cost; sessions report what they did
  • pending #25 P0-13: A session is judged on what it shipped, not its exit code
  • pending #29 P0-15: Dispatcher grants the permissions it compiled, and counts retri
  • pending #42 P0-17: Per-role dispatch credentials — least privilege, not one omnibu
  • pending #45 P1-3: Approval gates as policy — critical work waits for a person
  • pending #64 P1-9: Delivery Lead role pack — governance gets an owner
  • pending #100 BUG: approval-gate tests are path-filtered away from the files they as
  • pending #101 Governance: narrow the delivery-lead write scope, and scope the approv
  • approved #113 BUG: shipped-nothing gate fails open when a compiled pack has no produ
  • pending #128 The test-wiring handoff has blocked four PRs — remove it or queue it
  • pending #134 BUG: a by-design workflow-scope refusal is indistinguishable from a br
  • pending #168 P1-17: Check at refinement that a story's criteria fit the assigned ro
  • pending #174 check-test-wiring greps for strings, so discovered tests need a commen
  • pending #190 portal/ and adapters/ are in no role's write scope, so the new story-s
  • pending #202 P4-1: Declare the product registry — one place every product is define
  • pending #206 Build scripts/check-products.py against policies/products.yaml
  • pending #208 P4-2: Dispatcher targets a product repo, not only itself
  • pending #209 P4-3: Bootstrap a product repo — and verify it, rather than trusting t
  • pending #222 P4-7: Dispatch under a second harness — the compiler has two targets,
  • pending #224 Register a second product and run one story against it — the two-repo
  • pending #225 SECURITY: every required check runs the pull request's own code
  • pending #227 Every new product repo would start with the same unread-review hole
  • pending #228 CRITICAL: the product checkout deletes the control plane — every dispa
  • approved #232 Dispatcher builds the agent prompt from the issue's current content, n
  • approved #233 compile-pack.py: write_scope never reaches the agent prompt, and --che
  • approved #234 qa-gate.sh treats a failed label lookup as an empty (non-rejected) lab
  • pending #241 P4-7 follow-up: run the live codex trial dispatch.yml now supports
  • pending #246 CRITICAL: bootstrap requires a dod check the product repo cannot produ
  • pending #261 Wire check-products.py as a required status check on policies/products
  • approved #262 products.yaml: foundry-program and ai-sdlc-pilot share project board 2
  • pending #268 Two-repo dispatch: the product checkout's origin pointed at the contro
  • pending #269 Every claude-code session since 2026-09-08 21:47 UTC dies in under a s
  • pending #318 Developer pack: test, debug and slice before opening the PR (adapted f
  • pending #320 Role-pack skills reach dispatched sessions, on demand (P0-1)
  • pending #322 One GitHub App replaces the three PATs; a required check enforces who
  • pending #323 foundry-init: one idempotent command from empty repo to first dispatch
REQ-013 pending
  • pending #51 P1-6: Retro ceremony v0 — event-derived, one issue per window
  • pending #54 P3-1: Engineering memory in git notes
  • pending #103 P1-11: Architecture decision records — establish the format and backfi
  • pending #105 P1-13: ADR dashboard — render the decision records as a page
  • pending #119 P3-2: Engineering memory — the git notes store
  • pending #120 P3-3: Engineering memory — dispatcher writes and reads notes
  • pending #126 P1-15: ADR validator
  • pending #158 P3-5: Memory seam — MemoryStore contract behind the git-notes backend
  • pending #165 Engineering memory has never written a note in production — refs/notes
  • pending #194 P3-9: Exercise the engineering memory round trip — no note has ever be
  • pending #212 P4-6: Learning loop — the same correction was made seven times and non
  • pending #263 Build the recurring-correction detector decided in ADR-0010 (learning
  • pending #264 REQ-013 coverage notes: distinguish the store (built, exercised) from
REQ-014 pending
  • pending #27 P0-14: Programme status page — traced vs actually satisfied
  • pending #159 Self-hosting verdict is hardcoded 'unproven' while the page prints 46
  • pending #164 P1-16: Compute the self-hosting verdict, and catch notes that contradi
  • pending #200 BUG: session-end aborts on an unbound variable — 43 of 74 assertions r
  • pending #207 PILOT: one story, one product repo, issue to deployed, nothing untrack
  • pending #208 P4-2: Dispatcher targets a product repo, not only itself
  • pending #224 Register a second product and run one story against it — the two-repo
  • pending #228 CRITICAL: the product checkout deletes the control plane — every dispa
  • pending #244 PILOT: show when the status page was generated
  • pending #246 CRITICAL: bootstrap requires a dod check the product repo cannot produ
  • pending #268 Two-repo dispatch: the product checkout's origin pointed at the contro

Out of scope here (PRD §8): coverage trend, defect density and a flake list all need escaped-defect tracking and CI flake history that do not exist as computable inputs yet. A per-sprint cut is likewise out of scope — there is no populated sprint field to group by.