Decide where to break a system apart, on evidence. Use when splitting a monolith, planning a strangler or service extraction, sizing the facade an extraction would need, finding seams or bounded contexts, judging which modules are genuinely coupled, grouping…
Decide questions about a codebase's logic that reading and traversal cannot. Use for business rules, rule engines, thresholds, configuration profiles, feature flags, pricing or billing formulas, and duplicated or contradictory calculations — whether a…
Work out what an unfamiliar or legacy codebase actually does, and what is safe to change. Use for legacy modernization, replatforming, a rewrite or strangler migration, onboarding onto an inherited system, technical-debt assessment, documenting what a system…