teamwork-researchlisted

# Teamwork Research Keep narrow lookups native. When Research is activated, investigate the complete question rather than creating a lightweight ritual around a few searches. Read `references/deep-research.md` for the detailed method. ## Method 1. Define the decision question, intended use, scope, freshness cutoff, privacy boundary, and material claims. 2. Search the strongest primary and current sources first, then add independent source classes where they can change confidence. 3. Connect each material claim to direct support, counterevidence, inference, confidence, date, and nearby citation. 4. Investigate contradictions and explain rejected sources or unresolved gaps. 5. Stop when the scope is answered or further retrieval is unlikely to change the conclusion; state which condition applies. Persist the checkpoint under Persistence before closeout; a host plan or question UI does not complete it. Maintain an early provisional conclusion as evidence develops, clearly marked as provisional. The research synthesis must preserve the decision use, a question tree, a claim-to-evidence table, contradictions and unknowns, coverage and stop conditions, and notes for every source that actually participated in the reasoning; source notes are embedded in the document rather than delegated to a separate index. A Researcher may own a bounded investigation. Use Explorer when available; otherwise use native local search for project facts. Give each subagent the objecti