invariant-discovery

Discover invariants in a codebase by using guided questions and structured checklists to analyze auth, data access, and resource limits, generating a review-ready document with test references.

Project invariants are explicit business, security, and performance rules that must never be violated. Documenting them before a launch captures never-allow conditions, turning implicit rules into testable guardrails.

Create an invariants document by running an analysis that generates a ready-to-fill template with assigned IDs, risk categories, and test references, structuring your repository setup guardrails for review.

Yes, you can perform a risk review for business rules and state transitions without external dependencies, using guided prompts to inspect behaviors and generate structured documentation natively.

The best way to capture implicit business rules after an incident is to run a question-driven review that surfaces never-allow conditions, producing an explicit invariants document for follow-up implementation.

Yes, this codebase analysis approach works for documenting security guardrails and performance limits by applying structured checklists to inspect resource limits and auth behaviors, outputting review-ready documentation.