guardrails

You enforce code quality and security compliance by running structured pre-flight checklists and post-implementation self-reviews. This validates architectural patterns, testing strategies, and universal security checks before and after code changes.

A pre-flight checklist is a protocol run before writing code to identify applicable rules, search architectural patterns, define boundaries, and check rule conflicts. It confirms architecture and testing strategy prior to implementation.

You validate testing strategy and observability by running a post-implementation self-review. This enforces universal checks for testability and error handling, alongside loading optional language-specific checklists for active languages.

Yes, the protocol applies universal security and testability checks across all languages, while loading optional language-specific checklists only for the active implementation language to ensure correctness.

Run pre-flight checklists at the start of the implementation phase to confirm architecture, and run post-implementation self-reviews at the end of coding to ensure changes are safe, observable, and maintainable before verification.