Dedicated ingest-health page/banner (richer surface beyond #174's badge + per-project indicator)

Dispatch

canonical · plan

Spec

markdown

hand-off · dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

Direct dispatch — no refine required. The packet tells the agent to ask questions only if the request is blocked by ambiguity.

target project worktree · optional branch · optional agent tool · optional session id · optional

kind

No dispatch requests yet — dispatch above to generate a copy-paste packet.

provenance · append-only

live

note added 1d ago

Spun out of #174 (operator Q&A #37, 2026-07-04 — operator asked for a "brief for potential dedicated health page/banner"). Idea: Beyond #174's top-nav ops badge + per-project /projects indicator, consider a DEDICATED ingest-health page (or persistent banner) as a richer surface: ingest queue depth over time, a per-project health table (the #174 classification: healthy_idle / healthy_ingesting / backed_up / stuck / no_sessions_in_window), stuck-tail drilldown (reuse flower:ingest-backlog), and alert history. "Potential" per operator — exploratory; validate the need once #174's badge + indicator land (they may suffice). Relation: builds on #174 (health classification = the data model) + #112 (visibility). Conceptually depends on #174 landing first. NOT yet scoped/planned.

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

epic · dependencies

epic parent

depends on

No dependencies — dispatchable once planned.

agents · waves

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.