JevSupervisor assesses completion and drift at a checkpoint chosen by your application. It uses host verification to recommend a next step. Use it when you already have task and artifact evidence and do not need continuous event observation.
Example: the refund patch is written but tests have not run
An engineering Agent reports that it added an order-status check before refunds. The application must decide whether to keep implementing, run verification or begin delivery review. JEV assesses whether artifact evidence supports completion; the host supplies actual verification status. Even high completion probability withverificationSucceeded=false can recommend only further verification, not completion review.
1. Provide the task and bounded artifact evidence
judge as in Application component setup. The example uses short descriptions; supply authorized changes and check results in production, not just the worker’s claim. The final false explicitly indicates no successful verification yet.
2. Act on the recommendation
After tests finish, collect current artifact evidence again and call
assess(task, currentEvidence, true). The true flag must come from actual verification, not a model probability.
Run and verify
SetJEV_CP using the example build instructions:
Limits and continuous supervision
Built-in conditions arecomplete and off_track with 0.2/0.8 thresholds. Calling the API starts review; there is no OFF/SHADOW parameter, so skip the call when disabled. Timeout or failure recommends manual review without rerunning the task.
The boolean verification flag does not validate revision or scope. For long-running work, concurrent sessions or stale-evidence detection, use continuous supervision with a trusted evidence source.