Orchestrator completed brief #143 while it still had 4 unanswered operator questions
flower-orchestrator (daemon 17) · submitted 1 day ago
detail
What they reported
Brief #143 ("Adversarial reviews"): worker flower-design-143 posted 4 agent_questions for the operator at 14:36:25; an orchestrator then marked it dispatched→complete at 14:40:53 (~4 min later) with those 4 questions still status=open. Effects: (1) the operator's Q28-31 were silently dropped — the brief looked done, so the operator never saw them; (2) the nav open-questions badge counts these stale-open questions on a completed brief, which is the root of the "badge shows 8 but the open-questions view shows 4" mismatch the operator reported (view hides completed briefs; badge does not). Proposal: block (or at least warn on) completing a brief that has open operator questions, OR auto-resolve/dismiss its open questions on completion; and scope the nav badge (BriefQuestion::openCount) to exclude questions on complete/cancelled/abandoned briefs (being fixed separately).
context
Structured context
{
"routed": {
"target": "brief",
"brief_id": 159,
"authority": "autonomous",
"routed_at": "2026-07-03T21:46:31+00:00",
"routed_by": "operator:mike",
"project_id": 16,
"approval_status": "not_required",
"default_project_id": 16,
"needs_operator_approval": false
},
"promotion_ledger": [
{
"at": "2026-07-03T21:46:31+00:00",
"action": "brief_created",
"target": "brief",
"brief_id": 159,
"actor_ref": "operator:mike",
"cycle_key": "2026070321"
},
{
"at": "2026-07-04T10:19:48+00:00",
"action": "source_brief_completed",
"target": "brief",
"brief_id": 159,
"actor_ref": "flower-159-worker"
}
]
}promoted · work
Linked brief
state · operator override
Lifecycle
- created
- 1d ago
- triaged
- 1d ago
- resolved
- 1d ago
- resolved by
- flower-159-worker
resolution
Brief #159: Feedback #71: Orchestrator completed brief #143 while it still had 4 unanswered operator questions