deepr-research

name	deepr-research
description	Use Deepr for bounded deep research, async cited reports, and consultation with persistent domain experts. Trigger when a user asks for current sourced analysis, a research cost preview, a domain expert or expert council, or inspection of durable beliefs, gaps, confidence, and provenance.
metadata	{"version":"2.37.0"}

Deepr research

Use Deepr as a bounded research and persistent-expert service. Preserve citations, budget posture, capacity provenance, uncertainty, and dissent.

Release-safe operating contract

Treat these as works-now surfaces in v2.36:

• One API-backed research job when the provider, model, tools, token ceilings, and price are all known.
• Explicit local Ollama or non-metered plan-quota expert workflows.
• Read-only expert state, handoffs, loop status, memory cards, and derived exports.
• One-expert or multi-expert consultation through explicit local or plan synthesis. Separately bounded API council synthesis is available only after explicit approval and a positive budget.

Treat these as execution-blocked, even if a tool or flag remains visible:

• deepr_agentic_research and other autonomous multi-round metered work.
• deepr_query_expert with backend="api" or agentic=true.
• Automatic cross-provider metered fallback.
• Metered batch, campaign, team, prepared, or continuation execution.
• Hosted upload, file-search, or vector-store attachment to research.
• Generic metered expert creation, learning, resume, refresh, gap fill, reflection, portrait generation, or corpus calibration.

Do not retry a blocked surface with a larger budget or another provider. A capacity gate means the accounting contract is unavailable, not that the user asked a bad question.

Select capacity explicitly

1. Prefer existing expert state when it already covers the question.
2. Prefer backend="local" for a true $0 marginal-cost expert turn when an admitted Ollama model is ready.
3. Use backend="plan" only with an explicit non-metered plan id. Do not infer that CLI presence proves free quota. Copilot is visible/read-only in v2.36.
4. Use one bounded API research request only after the user authorizes spend. Pass an explicit provider, model, and budget ceiling.
5. Never silently fall through between capacity classes.

Run one bounded research job

Use this sequence:

1. State that the budget is a maximum, not a predicted final charge.
2. Obtain explicit approval before a paid call.
3. Call deepr_research with one focused prompt, an explicit provider/model, and the approved budget.
4. Omit files in v2.36 because hosted research context is gated. Put compact non-sensitive context in the prompt or use local source packs outside this tool.
5. Monitor the returned job id or returned resource URI with deepr_check_status or a resource subscription.
6. Retrieve the completed report with deepr_get_result.
7. Report actual settled cost when available and preserve inline citations.

Do not invent fixed prices or promise a completion time. Model rates, tool charges, provider latency, and the hard request envelope determine the admission result. If the envelope exceeds the approved budget, stop and return the denial rather than weakening the ceiling.

Consult persistent experts

Start by calling deepr_list_experts and, when useful, deepr_get_expert_info. Then choose one of these no-metered paths:

deepr_query_expert(
  expert_name="Security Analyst",
  question="What evidence should guide this decision?",
  backend="local",
  agentic=false,
  budget=0
)

deepr_query_expert(
  expert_name="Security Analyst",
  question="What evidence should guide this decision?",
  backend="plan",
  plan="codex",
  agentic=false,
  budget=0
)

For several experts, prefer deepr_consult_experts with synthesis_backend="local" or synthesis_backend="plan". Keep the roster at 10 or fewer, preserve disagreements, and verify that capacity.live_metered_fallback is false.

An expert answer is a perspective over stored state, not ground truth. Surface confidence, contested beliefs, stale evidence, missing sources, and known gaps. Do not claim that a fresh research report was permanently absorbed unless a separate verified write workflow actually completed.

Handle local capacity defensively

For scheduled local maintenance, treat busy as a waiting outcome. Preserve the returned retry time and do not fall through to plan or API capacity. Expected retry guidance uses bounded 30-minute, 2-hour, then 6-hour cadence. Explicit unscheduled local work is an operator override; do not simulate that override on the user's behalf.

Present results

• Lead with the answer.
• Preserve every citation marker and source URL returned by Deepr.
• Separate research-derived claims from your own inference.
• Include provider/capacity, actual settled cost, and important limits.
• Preserve council dissent instead of flattening it into false consensus.
• Say when semantic quality is unreviewed. Structural eval success is not proof that an answer is true or wise.

Tool guide

Tool	Use
deepr_tool_search	Discover a current tool schema before calling it
deepr_status	Inspect service readiness and spending posture
deepr_research	Submit one bounded paid research job after approval
deepr_check_status	Inspect an accepted job
deepr_get_result	Retrieve a completed cited report
deepr_cancel_job	Request cancellation and retain accounting state
deepr_list_experts	List persistent experts
deepr_get_expert_info	Inspect expert profile and gaps
deepr_query_expert	Run one local or plan read-only expert turn
deepr_consult_experts	Produce a bounded one- or multi-expert consult artifact

Error handling

• BUDGET_EXCEEDED or BUDGET_INSUFFICIENT: return the required ceiling and ask whether the user wants to approve a new bounded attempt.
• PROVIDER_NOT_CONFIGURED: identify the missing explicit capacity without switching providers.
• metered_expert_chat_accounting_unavailable or another capacity block: use local/plan read-only consultation or stop.
• Busy local capacity: report the durable wait and retry time.
• Ambiguous provider failure: do not resubmit automatically. The reservation may have been conservatively settled.

Read these only when needed:

• Research modes for the exact works-now and gated research boundary.
• Expert system for read-only consultation and verified update boundaries.
• Cost guidance for ceilings and ledger rules.
• MCP patterns for discovery, resources, and host-agent contracts.
• Troubleshooting for typed failure handling.
• Prompt patterns for bounded research prompts.