Aglet

Prioritize Verification Work for an Agent Task

Prioritizing verification work means deciding which proof closes the most important risk first. Rank checks by consequence of an undetected failure, likelihood of change, evidence readiness, reversibility, and review cost. Keep low-impact polish separate from checks that determine whether the task is acceptable.

Decide where the work belongs

  1. Rank acceptance risk

    For each missing check, record the behavior or decision it protects, the failure it could reveal, and the impact of accepting a false result. Prioritize data integrity, boundary behavior, and contract changes before optional presentation or explanatory checks.

  2. Assess proof readiness

    Identify fixtures, current samples, queries, comparisons, reviewer time, and environment needed for each check. Classify the next move as define a criterion, collect evidence, run a bounded review, request an owner, or defer. Record freshness and coverage limits.

  3. Choose queue and gate

    Set the first verification item, owner, evidence cutoff, expected result, and blocking status. Add a trigger for widening coverage when a check fails or reveals a new boundary. Do not declare the task ready because one easy check passed while material proof is absent.

What to carry forward

Return a ranked verification queue with acceptance risk, check, evidence source, owner, blocking status, and failure trigger. The leading item should explain the decision it protects. Mark the queue provisional when the expected outcome or reviewer authority is still unclear.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow