Draw
Bind a reproducible sample to one exact, finite trace population.
Governed evaluators for AI systems.
An LLM judge is easy to write. The difficult part is establishing what it measures, which human evidence supports it, how disagreements were resolved, and which exact evaluator version produced a result.
Coeval makes that work first-class. It turns representative traces into narrow criteria, governs human review and evaluator versions, validates them against protected truth, and emits evidence that downstream systems can verify without inheriting release policy.
Agent “The deployment is complete and available at the production URL.”
Evidence Command returned before the deployment health check completed.
The success claim exceeds the evidence available at the point it was made.
“Human truth” is not one mutable score in a database. It is a governed chain of evidence.
Evaluator quality cannot be separated from the reference evidence used to validate it. If reviewers see one another’s labels, if ambiguous examples are forced into pass or fail, or if adjudication silently overwrites the original disagreement, the final metric becomes more confident and less trustworthy at the same time.
Coeval keeps independent labels, abstention, disagreement, alignment, and adjudication as append-only evidence. That history makes it possible to understand not only the final answer, but how stable the criterion was and where reasonable people differed.
Bind a reproducible sample to one exact, finite trace population.
Turn observed failures into a taxonomy and narrow, versioned criteria.
Collect independent labels, abstentions, disagreements, and adjudication.
Compare a pinned evaluator against protected human truth.
Produce policy-free evidence with exact provenance and completeness.
A broad “quality” judge obscures which behavior moved and why. Coeval keeps criteria narrow and versioned, then pins evaluator execution to that identity. Changing the criterion, prompt, model, or protected reference set creates new evidence rather than rewriting old results.
Suite manifests and assessment receipts preserve criterion identity, execution provenance, coverage, and completeness. They intentionally do not say whether a release should ship. That decision depends on customer policy and belongs downstream—in a tool such as Dailies.
Coeval can import traces from LangSmith and LangFuse-compatible sources, integrate with Ironside as the system of record, and expose project-scoped machine access. The system is built around evidence portability rather than requiring every adjacent concern to live inside it.
Human labels can still be noisy, criteria can still be incomplete, and evaluator behavior can change with models and providers. Coeval’s job is to make those dependencies inspectable and versioned—not to erase uncertainty. It also does not encode release thresholds or compensation rules; those remain policy owned by the system consuming its evidence.
Read the v0.1.0 release ↗