meta-codelisted

# meta-code Answer the current user request. ## Objective Produce a grounded development answer with the smallest source and verification topology that can support it. `ROUTE -> COLLECT -> SYNTHESIZE -> VERIFY/OUTPUT` For SIMPLE work, do not print phase headers. For STANDARD and DEEP work, print one compact progress line per phase. Never narrate skipped agents or routine checks. ## Profiles Select the lowest profile that covers the source count, uncertainty, and risk. | Profile | Use when | Total helper cap | Verification | |---|---|---|---| | SIMPLE | Stable single-hop answer, one local question, or one exact source | 0-1 | Orchestrator self-check | | STANDARD | Two or three answer obligations, mixed local/docs/web evidence, or contextual how-to | 0-2 | Orchestrator self-check | | DEEP | Architectural or multi-hop analysis, high-stakes decision, unfamiliar domain, volatile comparison, or genuinely contested evidence | 0-3 including verifier and refinement | Orchestrator self-check plus at most one independent verification mode | Helper caps cover the entire run. A challenge, evaluator, or refinement consumes one slot. Never exceed the cap because a prior helper failed. ## Source routing | Need | Route | |---|---| | Stable fact or conceptual reasoning | Direct synthesis | | Current project behavior | Targeted `rg` and file reads with `file:line` evidence | | Bounded codebase flow | Built-in `explorer` only when direct reads are insufficient | | Broad cross-module a