semantic-consistency-audit

Cross-contract semantic inconsistencies are detected by analyzing shared variables, formulas, and magic numbers to surface unit mismatches and formula drift. This automated audit enforces consistency checks to prevent subtle bugs and funding errors across in-scope contracts.

Cross-contract semantic drift occurs when shared config variables, formulas, and magic numbers diverge across multiple contracts. Identifying this drift prevents subtle bugs and funding errors by enforcing consistency checks for unit mismatches and formula variations.

Yes, you can audit magic number drift across EVM, Solana, Aptos Move, and Sui Move projects. The audit enforces checks for magic-number drift by comparing contract inventories and constraint variables to generate structured findings.

Audit shared variables and formulas by comparing contract_inventory.md and constraint_variables.md across in-scope contracts. This process surfaces HAS_MULTI_CONTRACT findings related to formula drift, unit mismatches, and magic-number drift.

The best way to prevent unit mismatches is to run a semantic consistency audit that enforces cross-contract consistency checks. It compares shared variables and formulas to output structured findings detailing root causes and recommended fixes.

Cross-contract audit findings are output to a structured report named niche_semantic_consistency_findings.md. This report details root causes and recommended fixes for detected unit mismatches, formula drift, and magic-number drift.