#78 build — clickable/slug entity references across flower UI (copy-ref + clickable id/slug labels + linked-context anchors)

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

OPERATOR GREENLIT 2026-07-03 (inbox note #2). Build the #78 recommendation (see brief #78, event 1606). Settled scheme: canonical open = flower HTTP links (APP_URL); solo:// only addresses native Solo resources, NOT flower entities. Ref convention: projects=slug; briefs/feedback/sessions/daemons=numeric id (keep #id visible). Inline-link policy (respects operator no-bloat constraint): compact plain refs by default, emit a link only on first mention in a checkpoint/handoff or a small `Refs:` block. Thin-slice UI to build: (A) a shared copy-reference action, (B) make existing id/slug labels clickable, (C) surface already-linked context as anchors. The recommendation also proposed 4 follow-up build briefs. REFINE: please decompose this into PR-sized build briefs (like #95) — the 3 thin slices A/B/C plus the 4 follow-ups — dependency-wired; then the orchestrator dispatches. Full recommendation lives on brief #78, event 1606.

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

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.