cross-module-consistency-auditor

To audit cross-module consistency, map the change kernel's blast radius across persistence, APIs, and reports to generate an impact map. This identifies affected touchpoints and defines invariants like aggregation reconciliation and state transitions for a testable consistency matrix.

A consistency matrix converts consistency rules into a rules-versus-modules checklist with PASS, FAIL, NOT TESTED, or N/A outcomes. It tracks expected versus current states across copied implementations and assigns owners for action items to ensure no touchpoint is missed.

To review copied logic efficiently, select a canonical implementation and apply a diff-based review strategy to replicated instances. This copy propagation review catches divergence across modules while avoiding redundant effort on duplicated code.

When auditing cross-module changes, check invariants including aggregation reconciliation, sign inversion, state transitions, tax and rounding, permission visibility, and report-versus-drill-down matching. These consistency rules ensure the change is uniformly applied.

During impact analysis, capture uncertain modules as NEEDS CONFIRMATION and track missing touchpoints to be resolved. This open-questions capture ensures unresolved areas of the cross-module propagation are explicitly logged for follow-up.

Yes, you can turn consistency rules into testable assertions for a test checklist. These assertions include totals reconciliation, sign inversion checks, report versus drill-down matching, and state transition checks to verify the specification change.