product
Engineers using Simplify Codebase in a desktop coding-agent workflow. They need to locate accidental complexity, understand confirmed ownership and consumer paths, judge a proposed cut, and verify a completed structural change. They need a concise analysis entry point before they can interpret the visual; they do not need the full proof record duplicated inside it.
Turn a proved Simplify Codebase Finding into a direct visual investigation surface. Success means the user can see where the problem lives, what reaches it, what would disappear, and what survived, while the written proof record remains the authoritative detailed report.
Direct, evidential, technical. Preserve Archify's crafted engineering-diagram identity while making cleanup decisions feel purpose-built rather than added on.
- explanatory card walls that repeat what the graph already shows;
- generic SaaS dashboards and decorative metrics;
- cleanup actions hidden behind general diagram controls;
- an Archify clone that lacks Simplify Codebase semantics;
- dense prose permanently occupying the investigation canvas.
- Let the graph own topology and state; use concise text to orient and interpret it.
- Make Locate, Trace, Cut, and Decide the visible primary workflow.
- Keep the Finding summary visible once, then reveal proof, consequence, and uncertainty at the decision point.
- Keep the graph dominant when evidence opens; decision text belongs beside the graph instead of pushing it below the fold.
- De-emphasize contextual semantics in readable gray instead of hiding them.
- Load into a stable graph. Motion may explain an explicit stage change, but never pulse or scan the report decoratively on entry.
- Keep source loci and stable Finding IDs available throughout the investigation.
- Make node selection unmistakable and preserve Archify's native focus links.
- Never imply that authored reachability proves runtime impact or deletion safety.
Preserve keyboard navigation, visible focus, reduced-motion behavior, and the existing Archify semantic labels. Never use color as the only signal for node role, cut state, confidence, or risk. The visualization is intentionally designed and accepted for desktop viewports only.