Why it matters
Cisco’s open-source Quarry compiles rules over messages, tool calls, results and event order, with optional model signals. Its examples detect a private-data read followed by external communication and include a reversed-order negative case. The alpha framework returns matching evidence; applications still own enforcement. Example model stubs are not production detectors.
My takeaway: Pin a reviewed version and start with local positive and benign fixtures. Preserve tool-call relationships and session history, test reordered and missing events, and verify how incomplete scans are handled. Keep rules and credentials outside agent control. Review false positives before connecting findings to blocking, and redact sensitive trace content in diagnostics.