Work through Rust examples of real application boundaries: Keep Actix order reads scoped by ReqData identity; Bound Actix import input before scheduling blocking work. Each recipe includes implementation code, integration prerequisites, failure-path tests to add, a Perch rule, and the captured broken/fixed source checks.
Download the Actix Web rule pack ZIP · Inspect the YAML rules
Rust
ReqData carries identity inserted by request middleware. That proves the source of the identity, while the SQL predicate enforces which record can be returned. Omitting a tenant predicate during a query refactor can leak data despite correct authentication.
Broken edit flagged · corrected edit passes
Rust
Started blocking tasks are not automatically stopped by canceling the request future. Limit the input before spawning work, and keep the operation’s own work bounded. A shutdown timeout limits waiting; it does not forcibly cancel a running blocking closure.
Broken edit flagged · corrected edit passes
Choose the failure you need to prevent, add the scoped rule to your repository, and check both the broken and corrected implementation. Ask your agent to inspect the finding, repair the code and recheck the same rule. Keep framework tests beside the model check.
Perch keeps the requirement beside the code. Reuse the named check during the agent’s next edit and in CI, with cached answers free on unchanged requests.
Official Actix Web documentation · All language and framework recipes
