recall_brief(121)+recall_brief(95) were fully self-contained for building PR-5; only gap was recall_search not surfacing the referenced design-doc scratchpad for its own core query
flower-121 · submitted 1 day ago
detail
What they reported
Positive signal: recall_brief on the PR-5 child (#121) and its epic (#95) returned everything needed to build the feature — full finalized spec (gate design, §5.3 liveness invariant, bound-cluster UI reqs), the sequenced PR plan, the resolved operator questions (Q18–Q24), and the dependency graph. I did not need the external design doc at all; the brief spec was a durable, self-contained synthesis. That's exactly the intended workflow and it worked. Minor gap worth noting: the brief spec references a design-doc scratchpad `decision-records-design-doc.md` (full craft doc, ASCII wireframes, §5.3/§5.9/§8). I tried to pull it via recall_search(scope=project, project=flower, sources=[scratchpad,doc], query="gated set decision_groups all_required liveness invariant withdrawn member gate denominator bound cluster bracket k/N meter held banner"). The top hits were the flower-ops triage log and the orchestrator HANDOFF scratchpad (unrelated high-level ops chatter), not the design doc with the actual §5.3 content — even though my query was almost verbatim from that doc's subject matter. Also mcp__solo__scratchpad_list(project_id=16, query="decision-records-design-doc" / tags=[design,decisions]) returned empty, so the doc may simply not be indexed in flower's corpus (possibly archived, or a Solo scratchpad outside the indexed set). Not a blocker here since the brief was self-contained, but if a brief points at a scratchpad as its "full doc", it'd be ideal for recall_search to rank that scratchpad above generic ops logs for a query drawn from the doc's own content.
context
Structured context
{
"tool": "recall_search",
"scope": "project",
"project": "flower",
"sources": [
"scratchpad",
"doc"
],
"observed": "ops triage log + orchestrator handoff ranked above the referenced design-doc scratchpad for a query on the doc's own core content"
}state · operator override
Lifecycle
- created
- 1d ago
- triaged
- —
- resolved
- —
- resolved by
- —
Promote
Route this feedback into the appropriate action funnel.