business-logic-guardian

To prevent breaking business logic during code fixes, validate planned changes against documented business rules before committing. This process checks modifications to application code behavior and flags any alterations that contradict existing edge case documentation.

Business logic behavior preservation is the process of verifying that code changes do not silently alter documented business rules. It checks code modifications against existing application logic documentation to catch conflicts and flag behavior changes before deployment.

Yes, code change validation requires a business logic documentation file to operate. You need either a business-logic-index.md AI retrieval file or a business-logic.md human narrative document stored in your docs folder, otherwise validation does not run.

To check code changes against business logic documentation, run a validation check when working on fixes that touch app behavior. The process compares planned code modifications against stored business rules and explicitly flags any behavior that would be removed or contradicted.

If there is no business logic file in the docs folder, the validation process functions as a silent no-op. You must have a business-logic-index.md or business-logic.md file present in the docs directory for the behavior break flagging to activate.

Yes, when behavior break flagging identifies a conflict, you can update the business logic documentation in the same change. This ensures your code modifications and business rules remain synchronized without unexpected user-facing behavior.