Skip to main content
Agent Eval 0.18.0 is on Maven Central. Maven coordinates and Java packages still use agent-judge and io.github.markpollack.judge.
Use the least intelligent practical evaluator that establishes the property at the reliability you need. Keep the compiler, ordinary JUnit, and available deterministic analyzers for facts they can settle. Supply a bounded evidence bundle when a written requirement needs judgment.

Add the dependencies

You need Java 21. Most callers need the core API, the explicit Jackson 2 codecs, the model-backed requirements, and the fluent assertions:
Add the runtime, execution and bridge modules you use from the inventory below. The requirements example has a complete caller POM and executable Java example with deterministic responses. For the PetClinic walkthrough, use the tutorial’s case-study run guide and presenter runbook; they cover IntelliJ, offline replay and caching. No live inference is required.

Build from source

To build the released source yourself, check out tag v0.18.0 of the Agent Judge repository and run ./mvnw -B -ntp clean install with Java 21. This installs the complete reactor, including the parent and every module, into your local Maven repository with tests enabled.

Configure, execute, retain

  1. Define or read the actual Requirement and its immutable source/revision.
  2. Select prepared evidence, an acquisition supplier, or a native investigative runtime configured with workspace/tools.
  3. Construct a ready Judge or Jury using typed builders.
  4. Execute judge() or vote(), or one cached AssertJ stage.
  5. Keep the whole result and optionally request an application reliance policy.
  6. Store/reopen V6 results with the explicit Jackson support module.

Dependencies

All artifacts retain group io.github.markpollack and are released at version 0.18.0. The AgentWorks BOM does not yet manage 0.18.0, so declare the version explicitly. The inventory is 14 JAR modules plus agent-judge-parent (POM packaging). The 0.18 migration guide explains the intentional API and wire breaks. The fundamentals path still demonstrates released 0.17.0 in its separate reactor. The PetClinic path demonstrates configured 0.18 APIs. For historical consumer changes, keep the 0.17 migration guide at its original semantics.