Skip to content

Task completion verification with decision models

Checking whether an agent's "done" claim is backed by evidence such as passing tests or changed files. It catches premature stops in coding agents.

69 public projects · page 3 of 3

  • Experimental protocol that checks the evidence behind a worker agent's PASS or BLOCKED report, with Jev answering narrow evidence questions.

    ProjectresearchPython
  • Open lab on using Jev routing in front of Claude Code correctly: measured bugs and patch, hard fallback, completion gate.

    Projectresearch
  • Production control plane for OpenClaw agents: Jev routes each Slack message to its task, with Temporal workflows, an evaluator and memory.

    LibraryproductionPython
  • Stop hook for Claude Code and Codex that refuses 'done' until a check passes after the last edit; Jev advises but never causes a block.

    CLIbetaTypeScript
  • Pi agent harness where Jev routes the model tier, picks runbook sections, gates tool calls and verifies reports on Neon Postgres.

    LibraryresearchTypeScript
  • Ten runnable JavaScript lessons where Jev judges agent situations like memory conflicts and handoffs while code enforces explicit policy.

    DemoprototypeJavaScript
  • Next.js app and GitHub Action where one parallel Jev call judges whether a pull request does what it claims, with policy in code.

    DemoprototypeTypeScript
  • Software development framework for coding agents that hands dependency vetting, completion gates and debugging decisions to Jev.

    Library
  • Chinese X post describing a workflow that asks Jev yes/no, either-or and score questions to decide when work is finished.

    Discussiondiscussion