What problem does it solve? Codebases touched by many AI coding sessions and tools (Claude, Cursor, Copilot, Windsurf) accumulate silent drift: reversed fallback orders, duplicate implementations that disagree, dead code, and documentation that no longer matches behavior. No single session ever notices these mismatches because each one lacks memory of the others. ## Core Features & Use Cases - Drift Detection Across Eras: Reconstructs commit history into eras and compares how the same responsibility was implemented across sessions, surfacing reversed fallbacks, duplicate logic, and order-dependent race conditions. - Four-View Drift Registry: Maintains a cross-referenced registry organized by finding, file era, responsibility, and risk severity so anyone can answer "is this file safe to build on?" at a glance. - Mandatory Standalone Checks: Traces state-existence assumptions across every event/webhook handler and tracks what money/quantity values actually represent (cents vs dollars, UTC vs local) end to end. - Use Case: After six months of mixed AI-assisted development, run an audit to find that orderService.js and orderController.js resolve the same fallback in opposite order — a Critical data-integrity bug no linter would catch. ## Quick Start Audit this repository for cross-session drift and produce a drift registry with findings prioritized by severity.
