Skip to content

Add escalation check: research asks before upgrading to deep-research - #19

Merged
5uck1ess merged 1 commit into
mainfrom
fix/research-escalation
Apr 5, 2026
Merged

Add escalation check: research asks before upgrading to deep-research#19
5uck1ess merged 1 commit into
mainfrom
fix/research-escalation

Conversation

@5uck1ess

@5uck1ess 5uck1ess commented Apr 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds an escalation check to the research skill after the corroboration step
  • If sources conflict, stakes are high, or confidence is low, asks the user before upgrading
  • Never auto-escalates — always asks first to avoid burning tokens

Escalation triggers

  1. 3+ CONTESTED claims (sources actively contradict)
  2. High-stakes domain (security, architecture, compliance, financial)
  3. User expressed uncertainty ("is this actually true", etc.)
  4. Most claims UNCORROBORATED (>50% single-source)

Test plan

  • Run research on a simple question — should NOT trigger escalation
  • Run research on a controversial topic — should offer to escalate
  • Verify user can decline and get standard synthesis

…-research

After corroboration, evaluate whether the question needs ACH-level rigor.
Ask the user to upgrade if: 3+ contested claims, high-stakes domain,
user expressed uncertainty, or most claims uncorroborated. Never
auto-escalate — always ask first to avoid burning tokens unnecessarily.
@5uck1ess
5uck1ess merged commit df35902 into main Apr 5, 2026
1 check passed
@5uck1ess
5uck1ess deleted the fix/research-escalation branch April 5, 2026 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant