Decisions
What is waiting on a human, and what was decided, computed from open needs-human and status:needs-refinement items the gate classifies critical (scripts/gate-check.py), open pull requests, and the status:ready label events that gate-check.py --enforce itself reads as approval. A reason or actor this page cannot determine is shown as unknown — never omitted, never guessed.
15
waiting on you
5
past SLA
90
decided
Waiting on you
Oldest wait first.
| Item | Why | Waiting |
|---|---|---|
| #194 P3-9: Exercise the engineering memory round trip — no note has ever be | pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
1034.0h past 24h SLA since `needs-human` was applied |
| #264 REQ-013 coverage notes: distinguish the store (built, exercised) from | changes_requirements — mentions `requirements/coverage.yaml` A REQ is a commitment. An agent proposing one is useful; an agent committing to one on the org's behalf is not its call. |
660.2h past 24h SLA since `status:needs-refinement` was applied |
| #261 Wire check-products.py as a required status check on policies/products | pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
660.2h past 24h SLA since `status:needs-refinement` was applied |
| #268 Two-repo dispatch: the product checkout's origin pointed at the contro | pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
660.1h past 24h SLA since `status:needs-refinement` was applied |
| PR301 fix(dashboards): surface failed PR lookups; recover squash-merge trail | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
486.9h since the pull request was opened |
| #198 Exercise the sign-off gate live and record REQ-008's note (post-merge | changes_requirements — mentions `requirements/coverage.yaml` A REQ is a commitment. An agent proposing one is useful; an agent committing to one on the org's behalf is not its call. |
480.2h past 24h SLA since `needs-human` was applied |
| PR303 docs(requirements): REQ-008 note — sign-off gate exercised vs. merely | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
480.2h since the pull request was opened |
| PR319 feat(developer): test, fix red checks and slice before opening the PR | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
53.2h since the pull request was opened |
| PR328 feat(dispatch): agents ask a person and hear the answer (#321) | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
44.1h since the pull request was opened |
| PR327 feat(security): one GitHub App with per-role tokens, and a required sc | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
44.1h since the pull request was opened |
| PR326 Work items carry their product; orchestrator and board sync route per | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
44.1h since the pull request was opened |
| PR325 feat(dispatch): role-pack skills reach the session, on demand | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
44.1h since the pull request was opened |
| PR329 feat(onboarding): foundry-init takes a product from empty repo to firs | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
44.0h since the pull request was opened |
| PR330 chore(config): the control plane's owner and repo live in foundry.yaml | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
43.9h since the pull request was opened |
| PR333 feat(dispatch): codex sessions get the role's skills too, on demand | awaiting_review — The `merge` gate (policies/gates.yaml) is owner: human — an open pull request waits on a person to review and merge it. |
43.7h since the pull request was opened |
Decided
Attributed to the actor on the status:ready label event — the same fact the gate reads. A bot applying that label is never shown here.
| Item | Decision & why held | By | When | Artefact |
|---|---|---|---|---|
| #288 Ceremonies close the record they supersede | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-29T04:46:22Z | PR #295 |
| #246 CRITICAL: bootstrap requires a dod check the product repo cannot produ | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-07T01:06:46Z | PR #255 |
| #245 The published site silently stopped deploying three days ago | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-07T01:05:45Z | PR #247 |
| #244 PILOT: show when the status page was generated | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-07T01:01:15Z | issue #244 |
| #206 Build scripts/check-products.py against policies/products.yaml | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-07T00:54:16Z | PR #254 |
| #241 P4-7 follow-up: run the live codex trial dispatch.yml now supports | Approved to proceed (`status:ready`) touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. touches_credentials — mentions `FOUNDRY_` Credential scope is the one privilege a required check cannot claw back, because the check is what a wider credential can edit. changes_requirements — mentions `requirements/coverage.yaml` A REQ is a commitment. An agent proposing one is useful; an agent committing to one on the org's behalf is not its call. |
Shashank2577 | 2026-09-07T00:54:14Z | issue #241 |
| #236 BUG: security and operations are unroutable — missing from dispatch.ym | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-07T00:54:13Z | issue #236 |
| #216 Wire structural enforcement for the security veto (security-gate.sh / | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-06T15:29:51Z | PR #237 |
| #215 Build role-packs/security/ and role-packs/operations/ per ADR-0008 | Approved to proceed (`status:ready`) touches_credentials — mentions `gh secret` Credential scope is the one privilege a required check cannot claw back, because the check is what a wider credential can edit. production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-06T15:29:49Z | PR #238 |
| #227 Every new product repo would start with the same unread-review hole | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-05T17:35:57Z | PR #239 |
| #226 21 review findings on the foundational PRs were never read, answered, | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `branch protection` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-05T17:20:12Z | PR #240 |
| #224 Register a second product and run one story against it — the two-repo | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-05T17:07:05Z | issue #224 |
| #222 P4-7: Dispatch under a second harness — the compiler has two targets, | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-05T16:58:06Z | PR #242 |
| #212 P4-6: Learning loop — the same correction was made seven times and non | Approved to proceed (`status:ready`) large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-05T15:59:43Z | PR #221 |
| #211 P4-5: A security role and an operations role — nothing has ever review | Approved to proceed (`status:ready`) production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-05T15:59:16Z | PR #217 |
| #210 P4-4: More harness targets — one works, the criteria claim two | Approved to proceed (`status:ready`) large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-05T15:58:48Z | PR #213 |
| #209 P4-3: Bootstrap a product repo — and verify it, rather than trusting t | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-05T15:58:24Z | PR #214 |
| #208 P4-2: Dispatcher targets a product repo, not only itself | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. touches_credentials — mentions `PAT` Credential scope is the one privilege a required check cannot claw back, because the check is what a wider credential can edit. large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-05T15:58:21Z | PR #218 |
| #207 PILOT: one story, one product repo, issue to deployed, nothing untrack | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-05T14:12:58Z | issue #207 |
| #202 P4-1: Declare the product registry — one place every product is define | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-05T07:00:34Z | PR #205 |
| #193 P3-8: Wire the sign-off gate into the loop — the client layer has neve | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. production_or_release — mentions `production` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-04T17:05:25Z | PR #199 |
| #192 P3-7: Rewire sync-project.py through the tracker seam — it still calls | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T17:05:03Z | PR #196 |
| #190 portal/ and adapters/ are in no role's write scope, so the new story-s | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T17:04:17Z | PR #195 |
| #180 P1-18: Implement the DoD deferral form in dod-check and the dispatch p | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-04T16:39:18Z | PR #189 |
| #185 P1-19: status.py hardcodes a role list that has never matched the pack | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T15:43:14Z | PR #186 |
| #184 The PRD names the eighth role twice, so the page reports 7/8 forever | Approved to proceed (`status:ready`) changes_requirements — mentions `prds/` A REQ is a commitment. An agent proposing one is useful; an agent committing to one on the org's behalf is not its call. production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-04T15:42:53Z | PR #188 |
| #183 Exercise the production gate once deploy.yml is on main | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-04T15:08:25Z | issue #183 |
| #179 46 of 47 closed stories had no QA verdict — the veto is fine, the rule | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-04T13:36:23Z | PR #187 |
| #174 check-test-wiring greps for strings, so discovered tests need a commen | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
Shashank2577 | 2026-09-04T12:59:18Z | PR #182 |
| #173 Define a DoD deferral form so honesty does not fail the build (policy | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-04T12:07:55Z | PR #181 |
| #171 BUG: test-wiring fails on main — portal/test_build.py runs in no workf | Approved to proceed (`status:ready`) touches_governance — mentions `required status` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. changes_requirements — mentions `requirements/coverage.yaml` A REQ is a commitment. An agent proposing one is useful; an agent committing to one on the org's behalf is not its call. |
Shashank2577 | 2026-09-04T08:58:49Z | PR #175 |
| #168 P1-17: Check at refinement that a story's criteria fit the assigned ro | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T08:47:27Z | PR #172 |
| #165 Engineering memory has never written a note in production — refs/notes | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. production_or_release — mentions `production` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-04T08:35:14Z | PR #170 |
| #158 P3-5: Memory seam — MemoryStore contract behind the git-notes backend | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T08:33:55Z | PR #166 |
| #164 P1-16: Compute the self-hosting verdict, and catch notes that contradi | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T08:33:38Z | PR #167 |
| #159 Self-hosting verdict is hardcoded 'unproven' while the page prints 46 | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T06:37:40Z | PR #163 |
| #122 P2-8: Deploy workflow with a real production gate | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-04T02:47:15Z | PR #161 |
| #155 Commit-hygiene skill doesn't state the trailer-contiguity rule | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-04T02:43:50Z | PR #160 |
| #117 P2-5: Client portal — what was delivered and what needs signing | Approved to proceed (`status:ready`) large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-04T02:43:27Z | PR #162 |
| #157 Backlog refill — refine toward unsatisfied requirements | Approved to proceed (`status:ready`) changes_requirements — mentions `requirements/coverage.yaml` A REQ is a commitment. An agent proposing one is useful; an agent committing to one on the org's behalf is not its call. |
Shashank2577 | 2026-09-04T01:17:48Z | issue #157 |
| #150 BUG: DoD reports trailers missing when they are present but outside th | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
Shashank2577 | 2026-09-03T17:26:40Z | PR #156 |
| #148 P2-10: Validators for the environment ladder and sign-off policies | Approved to proceed (`status:ready`) production_or_release — mentions `rollback` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-03T17:22:35Z | PR #151 |
| #120 P3-3: Engineering memory — dispatcher writes and reads notes | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-03T17:14:40Z | PR #153 |
| #140 P2-9: Ceremony declaration validator | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T17:14:37Z | PR #149 |
| #115 P2-3: Planning, review and retro ceremony workflows | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-03T17:14:35Z | PR #152 |
| #134 BUG: a by-design workflow-scope refusal is indistinguishable from a br | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. touches_credentials — mentions `FOUNDRY_` Credential scope is the one privilege a required check cannot claw back, because the check is what a wider credential can edit. |
Shashank2577 | 2026-09-03T16:47:22Z | PR #154 |
| #129 BUG: a session that correctly finds nothing to change is marked a fail | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
Shashank2577 | 2026-09-03T16:43:10Z | PR #145 |
| #128 The test-wiring handoff has blocked four PRs — remove it or queue it | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. touches_credentials — mentions `FOUNDRY_` Credential scope is the one privilege a required check cannot claw back, because the check is what a wider credential can edit. |
Shashank2577 | 2026-09-03T16:41:35Z | PR #141 |
| #127 Three merges in a row conflicted on build.py's page registry | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T16:41:33Z | PR #138 |
| #126 P1-15: ADR validator | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T16:36:03Z | PR #137 |
| #113 BUG: shipped-nothing gate fails open when a compiled pack has no produ | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-03T16:35:58Z | PR #131 |
| #123 P3-4: Tracker adapter — GitHub and Jira behind one contract | Approved to proceed (`status:ready`) large_estimate — mentions `Estimate: L` Not a risk rule, a cost one. Large stories are where budgets go and where scope quietly widens; a person should see them first. |
Shashank2577 | 2026-09-03T16:35:56Z | PR #135 |
| #121 P2-7: Environment ladder declared as policy | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. production_or_release — mentions `deploy` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-03T16:35:54Z | PR #144 |
| #118 P2-6: Transcript to draft PRD and candidate requirements | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T16:35:50Z | PR #133 |
| #116 P2-4: Client sign-off as policy-as-code | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T16:35:48Z | PR #139 |
| #114 P2-2: Declare all five ceremonies as policy | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-03T16:35:46Z | PR #132 |
| #105 P1-13: ADR dashboard — render the decision records as a page | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T16:35:44Z | PR #130 |
| #103 P1-11: Architecture decision records — establish the format and backfi | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T16:35:42Z | PR #111 |
| #104 P1-12: Decisions dashboard — what is waiting on a human, and what was | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T07:37:40Z | PR #112 |
| #99 BUG: dispatcher marks a clean tracker-only session as failure when no | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-03T07:31:17Z | PR #108 |
| #98 P0-19: QA verdict dashboard — pass/fail matrix by requirement | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T07:31:15Z | PR #110 |
| #97 P0-18: Codex compiler target — compile_codex | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T07:31:12Z | PR #109 |
| #96 P1-10: Burndown & velocity dashboard | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-03T07:31:10Z | PR #107 |
| #92 BUG: dod-check must require a closing keyword, not a bare issue mentio | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T18:34:03Z | PR #94 |
| #91 BUG: the DoD accepts a work-item mention, so merged PRs leave issues o | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-02T18:30:52Z | PR #93 |
| #87 BUG: scripts requiring GNU coreutils fail for reviewers on macOS | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
Shashank2577 | 2026-09-02T16:45:51Z | PR #90 |
| #84 BUG: scripts/test-dispatch-session-end.sh runs nowhere in CI | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-02T16:19:40Z | PR #89 |
| #83 BUG: a successful session is trusted to move its own label, and often | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. production_or_release — mentions `rollback` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-02T16:09:59Z | PR #88 |
| #82 BUG: a rejected story never returns to a state its author can be dispa | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
Shashank2577 | 2026-09-02T16:08:28Z | PR #86 |
| #79 BUG: the orchestrator's eligibility ignores per-role dispatchable stat | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T14:32:33Z | PR #81 |
| #75 BUG: qa:rejected makes work permanently ineligible — rejected stories | Approved to proceed (`status:ready`) governance_role — label `role:delivery-lead` Delivery Lead is the one role whose write scope includes `policies/**` — the gates themselves. It exists because governance needs an agent owner, and it is safe to have one only while every one of its stories is approved by a person first. This rule is that condition, stated where it can be checked rather than left to the prose rules below. |
Shashank2577 | 2026-09-02T14:23:53Z | issue #75 |
| #58 BUG: session-end rollback leaves stale status labels and undoes a ship | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. production_or_release — mentions `rollback` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-02T14:01:46Z | PR #73 |
| #69 BUG: a test suite no workflow runs reported green | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. |
Shashank2577 | 2026-09-02T13:37:46Z | PR #85 |
| #68 BUG: a QA verdict landing after the last PR check leaves a stale green | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `.github/workflows/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-02T13:37:43Z | PR #80 |
| #67 BUG: the QA role cannot be dispatched — the guard requires status:read | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `required check` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-02T13:37:41Z | PR #74 |
| #59 P1-8: Document the approval gates and their SLA | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T13:19:29Z | PR #66 |
| #51 P1-6: Retro ceremony v0 — event-derived, one issue per window | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-02T09:35:27Z | PR #57 |
| #49 P1-4: Architect role pack v0 | Approved to proceed (`status:ready`) touches_credentials — mentions `token_secret` Credential scope is the one privilege a required check cannot claw back, because the check is what a wider credential can edit. |
Shashank2577 | 2026-09-02T09:35:22Z | PR #55 |
| #40 P1-2: Refinement trigger — dispatch the PM when the ready queue emptie | Approved to proceed (`status:ready`) pipeline_role — label `role:devops` DevOps is the only role that can edit the checks, budgets and dispatcher that constrain every other role. A pipeline change approved by the thing it governs is not a gate. touches_governance — mentions `policies/` These are the controls. A story proposing to change one needs a person to agree it should be changed, before a session spends a budget on it. |
Shashank2577 | 2026-09-02T08:34:46Z | PR #47 |
| #39 P1-1: Product Manager role pack v0 | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T06:47:24Z | PR #41 |
| #35 BUG: settings defaultMode is ignored; permission mode must be a CLI fl | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T04:23:07Z | PR #36 |
| #33 BUG: a crash in the spend diagnostics took down session end | Approved to proceed (`status:ready`) production_or_release — mentions `rollback` PRD §9: production sits behind a human gate and nothing an agent does unsupervised is irreversible. |
Shashank2577 | 2026-09-02T04:12:05Z | PR #34 |
| #31 BUG: the compiled allowlist cannot express a shell, and denials are un | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T03:54:29Z | PR #32 |
| #29 P0-15: Dispatcher grants the permissions it compiled, and counts retri | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T03:38:17Z | PR #30 |
| #27 P0-14: Programme status page — traced vs actually satisfied | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T03:12:30Z | PR #28 |
| #25 P0-13: A session is judged on what it shipped, not its exit code | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T03:05:41Z | PR #26 |
| #23 P0-12: Budgets measure cost; sessions report what they did | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T02:46:30Z | PR #24 |
| #20 P0-10: One GitHub credential + correct setup steps | Approved to proceed (`status:ready`) touches_credentials — mentions `PAT` Credential scope is the one privilege a required check cannot claw back, because the check is what a wider credential can edit. |
Shashank2577 | 2026-09-02T02:07:43Z | PR #21 |
| #18 P0-9: Generated tracker surfaces — project board sync + wiki publish | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-02T01:13:54Z | PR #19 |
| #9 P0-8: Orchestrator pack v0 — assignment loop | Approved to proceed (`status:ready`) unknown |
Shashank2577 | 2026-09-01T18:35:27Z | PR #17 |