blocker-validator

To validate task-blocker legitimacy, cross-reference agent attempt-logs against a predefined taxonomy of sanctioned and non-sanctioned blockers. This verifies that a failure actually occurred before allowing the task to be marked as blocked in the workflow.

Stop premature task abandonment by enforcing an evidence-based gatekeeper that requires structured attempt-logs. The validator distinguishes genuine blockers from avoidable hurdles, providing actionable feedback so agents remain productive instead of yielding prematurely.

Yes, the validation process operates within autonomous agent workflows to ensure consistent progress on Asana-tracked development tasks. It requires a local task GID and a reason string to determine if the claimed block is legitimate.

Yes, you need jq installed as a dependency to validate task blockers from JSONL attempt-logs. The validator also requires access to local state directories containing these logs and the ability to write verdict files for gatekeeper enforcement.

When an agent claims a missing test harness as a task blocker, the validator identifies it as an avoidable hurdle rather than a genuine blocker. It then provides specific, concrete next steps in the denied blocker feedback to keep the agent productive.

The best way to enforce gatekeeper rules is through adversarial verification that writes verdict files based on structured attempt-logs. This prevents agents from yielding on tasks by requiring evidence-based rulings before any block is accepted.