research

Evidence-based exploration guides you to observe running systems, collect source code observations, form hypotheses, and verify them with explicit tests. This structured approach reduces guesswork and accelerates understanding when investigating unfamiliar codebases.

Systematic code review involves observing the target codebase, exploring its module structure, and verifying assumptions with concrete tests. This method enforces standards like requiring 3+ independent sources to validate conclusions and produce reproducible findings.

Learning new technologies requires systematically examining modules, dependencies, and behavior to form actionable insights. You verify these insights by running experiments and tests to confirm or refute hypotheses with concrete evidence.

Structured exploration applies directly to debugging sessions and code reviews where deep understanding is required. It orchestrates evidence-based investigation by collecting observations, generating hypotheses, and verifying conclusions through explicit testing.

Evidence-based code exploration requires 3+ independent sources to validate conclusions and reduce guesswork. This standard ensures that observations from running systems and source code are confirmed through explicit testing before producing reproducible findings.

Summarizing codebase exploration findings involves producing concise, reproducible results and next steps for teammates. This follows the structured sequence of observing code, exploring dependencies, and verifying hypotheses with concrete tests.