Invariant Discovery & Enforcement

Discover and enforce system invariants by reading documentation, analyzing code paths, and distinguishing true invariants from incidental quirks before encoding them through types, validations, runtime guards, or tests. This process prevents regressions across domain flows by maintaining consistent scenario-level rules.

System invariants are critical conditions that must always hold true within domain flows. They require documentation when preparing fixes or updates, ensuring authentication, state shape, and lifecycle assumptions remain intact and fully logged for future agents to reference.

Document enforcement status by logging each critical rule's state, whether it is fully enforced through validations or tests, and identifying coverage gaps. Review requirements, PRDs, and tests to articulate and record the enforcement level for every invariant.

Yes, you can use prompt manager scenarios to confirm authentication, state shape, and lifecycle assumptions remain intact. The scenario focuses on invariant discovery and enforcement within local services to ensure development dependability without regressing behavior.

The best way to separate true invariants from incidental quirks is to study PRDs, requirements, and tests alongside available internal documentation. Articulate each condition clearly, then encode and verify the true invariants through types, validations, and runtime guards.