What problem does it solve? Before modifying an unfamiliar codebase, engineers need a safe, structured way to understand its architecture, public APIs, complexity risks, and project governance rules without changing any files. ## Core Features & Use Cases - Explorer Delegation: Dispatches the swarm's explorer agent to survey the repository, with an optional second pass focused on hidden requirements, unstated assumptions, and scope risks. - API Surface Analysis: Runs symbols or batch_symbols on key files to map public interfaces, and complexity_hotspots to flag modules needing security review or full gates. - Governance Extraction: Locates project instruction files (project-instructions.md, CONTRIBUTING.md, INSTRUCTIONS.md) in priority order and writes extracted MUST/SHOULD rules to .swarm/context.md. - Use Case: When starting a feature in a large multi-module repo, run this protocol to produce a context file capturing architecture, risk hotspots, and mandatory contribution rules before writing any code. ## Quick Start Ask the architect agent to run MODE: DISCOVER on this repository to map its structure, risks, and governance rules.