audit-context-building

Build smart contract audit context by analyzing source files line-by-line to map functions, invariants, and data flows. This structured pre-vulnerability process breaks down every function into purpose, inputs, outputs, and block-by-block reasoning to prevent missed invariants.

Skipping context building in code analysis causes hallucinations and missed invariants because auditors lose critical details without a stable mental model. A systematic line-by-line pre-analysis phase mapping cross-function dependencies preserves reasoning consistency before vulnerability hunting.

Yes, line-by-line context building supports DeFi protocols by tracking cross-function data flows and treating internal and external calls as a continuous execution flow. It maps every state variable, external call, and invariant across smart contract modules.

The best way to map invariants before auditing is applying structured checklists that enforce assumptions, first-principles, and 5 Whys/5 Hows analysis for each code segment. This micro-analysis format tracks dependencies across functions to ensure comprehensive coverage.

Yes, the context building approach handles dense functions and cryptographic logic by allowing sub-agent orchestration. It spawns dedicated analyzers for complex state-machine workflows and dense code segments to maintain granular analysis depth.

Line-by-line context building is not suitable when you lack access to source files or need rapid preliminary vulnerability scanning. It is a deep pre-vulnerability phase tool designed for thorough mapping rather than quick automated checks or surface-level reviews.