#95 PR-5 — Gated sets (decision_groups, all_required)

You are being dispatched from flower Brief #121: #95 PR-5 — Gated sets (decision_groups, all_required)

Recall pointer:
- Use recall_brief with id 121 for the full folder if you need provenance.

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/121-pr5-gated-sets
- worktree: not specified
- kind: fresh

Current brief spec:
## PR-5 — Gated sets (decision_groups, all_required) (child of #95)
`decision_groups` table + model + `DecisionGate` enum (`independent` / `all_required`).
Withhold-`released_at`-until-all-answered → release-together logic in `DecisionService`, **including the
§5.3 liveness invariant: a withdrawn member shrinks the gate denominator** so an `all_required` set can't
deadlock a looping daemon. Bound-cluster UI (accent bracket, `k/N` meter, held banner, `role="group"` +
`aria-describedby`).
Deps: PR-2 (#118, release logic) + PR-3 (#119, card). Design ref: #95 §5.3 / §5.9(Q1) / §8.
`php artisan test` green + pint. `Brief: #121` trailer.

Recent/key trace events:
[1] participant_joined flower-refine: (no body)
[2] note_added flower-refine: Child of #95. PR-5 of the 9-PR plan (§8 of the #95 design doc). Full spec via brief_update_spec.
[3] plan_proposed flower-refine: ## PR-5 — Gated sets (decision_groups, all_required) (child of #95)
`decision_groups` table + model + `DecisionGate` enum (`independent` / `all_required`).
Withhold-`released_at`-until-all-answered → release-together logic in `DecisionService`, **including the
§5.3 liveness invariant: a withdrawn member shrinks the gate denominator** so an `all_required` set can't
deadlock a looping daemon. Bound-cluster UI (accent bracket, `k/N` meter, held banner, `role="group"` +
`aria-describedby`).
Deps: PR-2 (#118, release logic) + PR-3 (#119, card). Design ref: #95 §5.3 / §5.9(Q1) / §8.
`php artisan test` green + pint. `Brief: #121` trailer.
[4] parent_set flower-refine: Grouped under epic #95.
[5] dependency_added flower-refine: Now depends on #118 (#95 PR-2 — Events, broadcasts, auto-participant + auto-link (decision_links)).
[6] dependency_added flower-refine: Now depends on #119 (#95 PR-3 — Four answer types + recommended + write-in (first Flux adoption)).
[7] status_change flower-refine: (no body)
[8] link_added flower-refine: (no body)
[9] link_added flower-refine: (no body)
[10] link_added flower-refine: (no body)
[11] participant_joined flower-119: (no body)
[12] unblocked flower-119: Unblocked — #119 reached complete.

Recommended linked context:
{
    "todos": [],
    "scratchpads": [
        {
            "id": 364,
            "solo_scratchpad_id": "1055",
            "name": "flower-refine — reset handoff (2026-07-03)",
            "archived": false,
            "revision": 1
        },
        {
            "id": 375,
            "solo_scratchpad_id": "1067",
            "name": "flower-refine — reset handoff (2026-07-03 #2)",
            "archived": false,
            "revision": 2
        },
        {
            "id": 378,
            "solo_scratchpad_id": "1070",
            "name": "flower-refine — reset handoff (2026-07-04)",
            "archived": false,
            "revision": 2
        }
    ]
}

Execution notes:
- Treat the brief as the source of truth.
- Keep work scoped to this dispatch request.
- Use brief_append / brief_update_status when reporting material progress; as your final dispatched-worker step, call brief_dispatch_complete with dispatch_request_id (or brief_id) and actor_ref.
- Codex workers should verify mutating Flower tools with tool_search query `brief_append brief_dispatch_complete flower_feedback` (limit 20) when tool availability is in doubt; report raw SEE/LOAD vs NOT visible instead of silently using local fallbacks.
- Add a git commit trailer `Brief: #121` to every commit for this brief so flower can exact-link commits back to the brief.