Ask Across Everything
Rule
Search Brain first, inspect federatedCoverage, then delegate live app-owned
questions to the owning specialist agent with call-agent.
Why
Brain owns cited company memory: reviewed knowledge, accessible raw captures,
and source records. It does not directly search Analytics, Mail/Gmail,
Dispatch, or sibling app databases. federatedCoverage is deterministic routing
metadata, not retrieved evidence.
Workflow
- Call
search-everything for broad questions, or use ask-brain when the
user asks a direct cited-memory question and wants an answer immediately.
- Read the Brain results and
federatedCoverage.scopeNote.
- Inspect
federatedCoverage.delegationHints and
federatedCoverage.discoveredAgents.agents. delegationHints[].target is
typed to exactly three values today: "analytics", "mail", "dispatch"
(FederatedDelegationTarget in server/lib/search.ts) — there is no
delegation hint for other templates yet, even if one is installed in the
workspace. Each hint also carries matchedSignals (which words in the
question triggered it) and a human-readable reason.
- If the user asked for live/app-owned data and a hint matches the request,
call the specialist app agent with
call-agent. Keep the prompt narrow and
include the user question plus any Brain context needed for names, dates, or
citations.
- Synthesize the final answer with clear source boundaries:
- Brain knowledge/captures are cited company memory.
- Specialist agent results are app-owned live data or app-native search.
- Coverage metadata only explains where you routed next.
- If no specialist agent is available, say Brain found a delegation hint but
you could not query that app in this workspace.
Routing Examples
- Product decision, policy, process, or "why did we decide..." -> Brain only.
Search Brain, open
get-knowledge / get-capture as needed, cite evidence.
- Dashboard metric, KPI, funnel, cohort, revenue, or chart -> Brain +
Analytics. Use Brain for context, then
call-agent Analytics for live
dashboard/data-source facts.
- Email, customer thread, sender/recipient, Gmail, inbox, or mailbox state ->
Brain + Mail/Gmail. Use Brain for durable context, then
call-agent
Mail/Gmail for mailbox-native search.
- Integration grants, reusable connections, secrets, approvals, recurring jobs,
workspace resources, or cross-app routing -> Brain + Dispatch. Use Brain for
documented decisions, then
call-agent Dispatch for current control-plane
state.
Don't
- Do not claim Brain searched sibling app databases directly.
- Do not treat
federatedCoverage.delegationHints as answer evidence.
- Do not invent live metrics, mailbox state, grants, or secrets from Brain
memory.
- Do not put A2A calls inside Brain actions; cross-app delegation happens in the
agent loop.
Related Skills
brain
delegate-to-agent
a2a-protocol
security
1---2name: ask-across-everything3description: Use when a Brain question asks across company memory plus live/app-owned data such as metrics, email threads, workspace grants, or secrets.4---56# Ask Across Everything78## Rule910Search Brain first, inspect `federatedCoverage`, then delegate live app-owned11questions to the owning specialist agent with `call-agent`.1213## Why1415Brain owns cited company memory: reviewed knowledge, accessible raw captures,16and source records. It does not directly search Analytics, Mail/Gmail,17Dispatch, or sibling app databases. `federatedCoverage` is deterministic routing18metadata, not retrieved evidence.1920## Workflow21221. Call `search-everything` for broad questions, or use `ask-brain` when the23 user asks a direct cited-memory question and wants an answer immediately.242. Read the Brain results and `federatedCoverage.scopeNote`.253. Inspect `federatedCoverage.delegationHints` and26 `federatedCoverage.discoveredAgents.agents`. `delegationHints[].target` is27 typed to exactly three values today: `"analytics"`, `"mail"`, `"dispatch"`28 (`FederatedDelegationTarget` in `server/lib/search.ts`) — there is no29 delegation hint for other templates yet, even if one is installed in the30 workspace. Each hint also carries `matchedSignals` (which words in the31 question triggered it) and a human-readable `reason`.324. If the user asked for live/app-owned data and a hint matches the request,33 call the specialist app agent with `call-agent`. Keep the prompt narrow and34 include the user question plus any Brain context needed for names, dates, or35 citations.365. Synthesize the final answer with clear source boundaries:37 - Brain knowledge/captures are cited company memory.38 - Specialist agent results are app-owned live data or app-native search.39 - Coverage metadata only explains where you routed next.406. If no specialist agent is available, say Brain found a delegation hint but41 you could not query that app in this workspace.4243## Routing Examples4445- Product decision, policy, process, or "why did we decide..." -> Brain only.46 Search Brain, open `get-knowledge` / `get-capture` as needed, cite evidence.47- Dashboard metric, KPI, funnel, cohort, revenue, or chart -> Brain +48 Analytics. Use Brain for context, then `call-agent` Analytics for live49 dashboard/data-source facts.50- Email, customer thread, sender/recipient, Gmail, inbox, or mailbox state ->51 Brain + Mail/Gmail. Use Brain for durable context, then `call-agent`52 Mail/Gmail for mailbox-native search.53- Integration grants, reusable connections, secrets, approvals, recurring jobs,54 workspace resources, or cross-app routing -> Brain + Dispatch. Use Brain for55 documented decisions, then `call-agent` Dispatch for current control-plane56 state.5758## Don't5960- Do not claim Brain searched sibling app databases directly.61- Do not treat `federatedCoverage.delegationHints` as answer evidence.62- Do not invent live metrics, mailbox state, grants, or secrets from Brain63 memory.64- Do not put A2A calls inside Brain actions; cross-app delegation happens in the65 agent loop.6667## Related Skills6869- `brain`70- `delegate-to-agent`71- `a2a-protocol`72- `security`