Lab Skills

---
name: deep-architecture-research
description: Deeply research technical architecture, source code, mechanisms, SDKs, frameworks, project comparisons, and system-design options across repositories, history, official docs, issues, discussions, and high-quality community signals. Use when the user asks for deep research, source-level understanding, architecture comparison, mechanism satisfaction, or evidence for designing a system. Always map the question and obtain confirmation before beginning substantive research; skip for simple factual lookups or straightforward implementation tasks.
---

# Deep Architecture Research

Outsource the legwork, not the problem definition. Work as a senior engineer reporting to a human architect.

## 1. Confirmation gate

Use one confirmation gate per research objective. A follow-up that stays inside an already confirmed scope continues without restarting the gate.

Before searching, cloning, or delegating substantive research, send a 500–1,000 Chinese-character framing brief in the user's language. Keep it near 500 characters when possible and include one compact box diagram.

The brief must make four things explicit:

1. **Objects**: what systems, projects, versions, or relationships will be studied.
2. **Questions**: the decisions, mechanisms, and satisfaction gaps to resolve.
3. **Dimensions**: orthogonal axes, layers, dependencies, boundaries, and scenarios.
4. **Sources and output**: repositories, history, docs, community signals, and intended artifact.

Use this shape, adapting labels to the task:

```text
┌──────────────┐     ┌────────────────┐
│ Research objects│──>│ Core questions │
└──────┬───────┘     └───────┬────────┘
       │                     │
       ▼                     ▼
┌──────────────┐     ┌────────────────┐
│ Dimensions   │────>│ Evidence/output │
└──────────────┘     └────────────────┘
```

End by asking whether the map is correct and what should be added or removed. Stop there. The gate is complete only after the user confirms or corrects the scope.

## 2. Research after confirmation

First, organize work by questions and mechanisms, not by vendor names. Define bounded work packages and the evidence each must return.

**MANDATORY — READ ENTIRE FILE:** Before gathering evidence, read [references/evidence-protocol.md](references/evidence-protocol.md). It defines source priority, local-clone practice, history windows, community use, evidence labels, and code-example rules.

Delegate independent work when it improves coverage or cross-checking. Each agent receives one bounded question and returns: