Feedback #42: Similar to the 'Orphaned' sub-menu item, let's do one for "Open Questions"
canonical · plan
Spec
hand-off · dispatch
Dispatch
Auto-dispatch
when it reaches planned
Design-loop
design pass before build
This brief is complete — dispatch is closed.
provenance · append-only
Trace
-
link added 3d agoagent · system:commit-trailer
-
participant joined 3d agosystem · system:commit-trailer
-
status change 3d agoagent · flower-orchestrator
-
participant joined 3d agosystem · flower-orchestrator
-
status change 3d agoagent · operator:mike
-
note added 3d ago
Operator approved this feedback-born brief for dispatch.
operator · operator:mike -
note added 3d agoagent · operator:mike
Feedback #42 Authority: OPERATOR APPROVAL REQUIRED Funnel: A - operator approved brief Gate: this brief must not be dispatchable until the operator approves it. Kind: idea Source: operator:ui Summary: Similar to the 'Orphaned' sub-menu item, let's do one for "Open Questions" Detail: Under Briefs that links to the /briefs view filtered to those with open questions? (left side nav) Context JSON: { "note": "/briefs" }
-
participant joined 3d agosystem · operator:mike
epic · dependencies
Relationships
epic parent
depends on
No dependencies — dispatchable once planned.
agents · waves
Participants
- operator:mike participant · active
- flower-orchestrator participant · active
- system:commit-trailer participant · active
trace · graph
Links
- Commit #1574 execution
scope
Projects
- flower · primary
dogfood · read-only
Agent’s-eye view
The literal recall_brief payload an agent gets — same service path as the MCP tool.