reversa-detective

You extract business rules from a legacy codebase by analyzing Git commit history and system contexts to reconstruct implicit domain validations, state transitions, and access control permissions into structured markdown documentation.

Generating retroactive ADRs from Git history involves analyzing commits for fixes, refactors, and reverts to reconstruct past decision rationale, turning implicit historical changes into reviewable architecture decision records.

Mapping state machines and RBAC from existing code requires analyzing entity lifecycles and domain constraints to document state transitions and generate permission matrices when access control is central to the system.

Yes, you can document implicit domain validations by extracting enums, constants, and TODO hints from legacy system artifacts and contexts, transforming unstated requirements into explicit structured documentation.

The documentation level generated when reverse engineering legacy behavior is gated by configuration settings, always producing a core domain markdown file while additionally deriving state machines, permission matrices, and retroactive ADRs based on the specified level.