business-logic-extractor

You can extract business logic by analyzing source code and tests to document entities, invariants, validations, and state transitions into a structured Markdown reference focused on product behavior rather than API calls.

The best way to document product behavior is generating an llms.txt-style reference that captures domain models, eligibility rules, and lifecycle transitions derived directly from the repository's source code and test assertions.

Yes, you can reverse engineer system behavior by scanning ORM models, guard logic, service layers, and tests to identify explicit invariants, side effects, and state transitions encoded within the application.

You generate a codebase documentation reference by performing a domain-first assembly into H2/H3 sections, clustering business rules like authorization thresholds and calculations into plain-English conditions backed by annotated code.

Yes, extracting domain models requires filesystem access to scan the codebase for cross-cutting middleware, config thresholds, migrations, and validation logic where business meaning is encoded.

Documenting business logic focuses on what the system does, such as eligibility and side effects, whereas API documentation explains how to call endpoints, making a domain reference more suited for product behavior understanding.