audit-context-building

Build deep architectural context for security audits by performing ultra-granular line-by-line code analysis using First Principles, 5 Whys, and 5 Hows to establish a stable mental model across modules.

The best way to perform line-by-line code analysis for vulnerability hunting is applying a structured workflow of Phase 1 orientation and Phase 2 micro-analysis to map thorough invariants and assumptions.

5 Whys analysis works during a code architecture review by driving ultra-granular micro-analysis of each function block, ensuring you capture cross-function dependencies and risk considerations before threat modeling.

Yes, you can maintain a persistent mental model across files and contracts during threat modeling by generating cross-function dependency outputs that track system-wide invariants and assumptions.

You need a structured workflow to map cross-function dependencies because it guides you from initial orientation through micro-analysis to global system understanding, preventing context loss across modules.

You should not use first-principles code analysis when you lack time for ultra-granular line-by-line reviews, as this method requires thorough micro-analysis to yield accurate vulnerability hunting context.