Uses of Package
dev.dokimos.server.service
Packages that use dev.dokimos.server.service
-
Classes in dev.dokimos.server.service used by dev.dokimos.server.controller.v1ClassDescriptionManages a project's regression-alert webhooks.Computes per-run, per-evaluator agreement between automated evaluator verdicts and human annotations.Service for human review annotations on run item results.Mints and manages scoped API keys.Service for server-owned versioned datasets.Builds the per-case run-diff view for the UI.Enqueues server-side judge jobs and reads the jobs registered for a run.Evaluates a CI regression gate by comparing an already-ingested candidate run against a resolved baseline run with the core
RunComparisonengine and returning a pass/fail verdict.Registers and reads LLM connections.Surfaces run items that still need a human verdict so a reviewer can work through a single queue instead of opening runs one at a time.Manages per-project trace eval rules.Persists OTLP traces and enqueues online evaluations for matching spans.Read side for ingested traces: a paginated list and a per-trace detail with spans and eval jobs. -
Classes in dev.dokimos.server.service used by dev.dokimos.server.serviceClassDescriptionShared entity-to-core conversion and run-comparison invocation for the regression gate and the per-case diff view.Result of comparing two runs: the engine output, the pairing strategy, and the runs' loaded item entities so callers (the diff view) can derive per-case input text without re-querying.Service for server-owned versioned datasets.The transactional steps of the judge worker, each in its own committed transaction so the worker can make the LLM HTTP call between them without holding a database transaction open.A detached view of an item result carrying only the fields the judge prompt needs.Pairs an eval result with the id of the item result it belongs to, for batch persistence.Resolves and protects the API key for an
LlmConnection.Pure translation from the OTLP/HTTP JSON request DTOs into the server's own span model, with no persistence.A span translated from OTLP, carrying the merged attributes and derived input/output text.The outcome of parsing: the valid spans and the count of malformed spans that were skipped.Published inside the run-completion transaction when a run regresses, and consumed only after that transaction commits.Computes, inside the run-completion transaction, whether a just-completed run regressed against its baseline, and publishes aRegressionAlertEventwhen it did.Decides which online eval jobs to create for a freshly ingested trace and persists them.The transactional steps of the trace eval worker, each in its own committed transaction so the worker can make the LLM HTTP call between them without holding a database transaction open.A claimed job paired with the span text snapshots the worker scores after the transaction closes.