adadrlisted

# ADADR Evidence-driven software architecture loop. ## Control-plane discovery gate Before architecture work, discover the project's canonical location or workflow for research, design, approval state, and implementation promotion. Use repository instructions, project configuration, or current authoritative project state. Do not invent a new `research/`, `design/`, `adadr/`, or approval directory just to satisfy this skill. If no canonical location/workflow is defined, or the defined location is not actually used by the project, stop before Analyze and ask the user to choose one mode: 1. **ADADR** — human-gated software design. Research approval and design approval are explicit user gates. 2. **Auto-RAGE** — the coding worker runs the complete ADADR software-design loop itself and records the research, design, review, decision, and verification evidence without stopping for user approval. Persist the selected mode in durable project instructions/configuration when authorized so future workers do not ask again. Never silently choose Auto-RAGE. ## Loop ### A — Analyze Establish the real problem before proposing architecture. Inspect current code/tests, existing research/design, recent changes, runtime evidence, relevant specifications, and serious alternatives. Separate verified facts, inference, contradictions, and unknowns. For defects, prefer a deterministic failing regression as primary evidence. ### D — Design Derive the smallest coherent design from the eviden