markusdowne/detectability-contract
Creates boundary-point validation contracts, defines invariant-based success criteria, and sets up automated verification probes so reliability workflows trigger on objective evidence rather than intuition. Use when designing robust handoff, memory-persistence, or tool-call reliability workflows; when you need to verify handoffs work, check memory persistence, validate tool calls succeeded, or convert vague reliability goals into concrete, testable checks at each boundary point with explicit failure-class mapping (operational vs. critical); or when you want to test your workflow end-to-end, make sure it works, or verify your automation runs correctly using read-back probes and escalation triggers rather than agent confidence. Includes explicit untrusted-content/prompt-injection guardrails for third-party inputs.
96
Quality
90%
Does it follow best practices?
Impact
98%
1.25xAverage score across 9 eval scenarios
task.mdevals/scenario-1/
Build a Reliability Detectability Contract
Your team has an agent workflow that writes state to disk, calls an external API, and performs pause/resume handoffs. Reliability incidents are hard to debug because failure conditions are not explicit.
Create a concise detectability contract artifact that defines boundary checks and escalation behavior.
Output Specification
Produce detectability_contract.md containing:
- A contract table with at least three boundary points.
- For each boundary: required invariants, verification probes, failure class mapping, and escalation trigger.
- At least one concrete executable-style check snippet (pseudo or real code) for validation.
- An explicit rule for unknown/unverifiable state.