concession-validator

You validate agent task abandonment by cross-referencing stated failure reasons against structured attempt logs and predefined taxonomy rules. This process ensures autonomous agents cannot prematurely give up on tasks without proving they hit a genuine technical wall.

Preventing incomplete work delivery requires enforcing an adversarial verification process for proposed concessions. This ensures that any delivery made without reaching full in-app success is backed by documented workarounds or sanctioned fallbacks.

Concession validation in agent governance is an adversarial gatekeeping mechanism that evaluates claimed blockers against structured attempt logs. It distinguishes between genuine technical walls and avoidable failures to enforce high-quality delivery standards in automated development workflows.

Yes, you need jq installed to use the concession validator. The skill requires jq as a dependency to parse local state directories containing attempt logs and execute verdict-writing logic based on specific concession categories.

You verify claimed blockers by invoking the concession validator for the current task ID and reason string. The validator cross-references these inputs against structured attempt logs to determine if the proposed block or downgrade is legitimate.

You should use adversarial gatekeeping when an agent attempts to mark a task as blocked due to a missing dependency or perceived error. It forces the agent to prove it attempted necessary workarounds, such as linking local branches or building test harnesses, before accepting the concession.