Work through Go examples of real application boundaries: Prevent privileged-field binding in an Echo profile mutation; Carry Echo cancellation through to the database query. Each recipe includes implementation code, integration prerequisites, failure-path tests to add, a Perch rule, and the captured broken/fixed source checks.
Download the Echo rule pack ZIP · Inspect the YAML rules
Go
Binding an HTTP body directly into a business model can expose fields the form never displayed. A dedicated DTO plus explicit mapping makes the mutable fields visible. The regression here is an agent extending the mapper with a privileged assignment.
Broken edit flagged · corrected edit passes
Go
A response timeout does not automatically stop a database query that never receives its context. Thread the request context through the adapter and select a database driver that supports cancellation. Do not substitute context.Background inside request-owned operations.
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 Echo documentation · All language and framework recipes
