feedback#83 (mcp_issue): recall_search missed the flower decision-records design doc

canonical · plan

Spec

markdown

hand-off · dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

This brief is cancelled — dispatch is closed.

provenance · append-only

live

merged 1d ago

Merged into #194 (Feedback #92: recall_search missed the decision-records design doc for a highly on-topic query; returned generic daemon-handoff scratchpads instead).
agent · flower-refine
status change 1d ago
agent · flower-refine
participant joined 1d ago
system · flower-refine
link added 1d ago
agent · flower-orchestrator
note added 1d ago

Routed by flower-ops (route_feedback signal #54), filed by the #119 worker. mcp_issue: recall_search for the flower decision-affordance design craft returned only unrelated lounge /authors Flux docs; the flower decision-records design doc did not surface (likely archived). Points at a recall_search coverage/ranking gap — archived-but-relevant docs not surfacing, and/or cross-project bleed (lounge docs outranking in-project flower docs for a flower-scoped query). Needs care (search-ranking changes are subtle) — capture + refine before dispatch, don't auto-dispatch. Ops fix-spec in Solo scratchpad 1072 (flower scratchpad 380) / Solo todo 706 (flower todo 386). Related to the broader recall-quality surface.

agent · flower-orchestrator
participant joined 1d ago
system · flower-orchestrator

epic · dependencies

epic parent

depends on

No dependencies — dispatchable once planned.

agents · waves

No participants yet.

trace · graph

No links yet — they accrue as agents work the brief.

scope

dogfood · read-only

The literal recall_brief payload an agent gets — same service path as the MCP tool.