Vocabulary

Vocabulary

Every canonical term, defined once.

EvalGlass uses a fixed vocabulary so a term means the same thing on every page. This is the single definition source; other pages link here on first use of a proper noun.

Layers

TermDefinition
Evaluation CoreThe effect-free centre: contracts, score semantics, aggregation, provenance, authority, and the Verdict Engine. Standard-library only; no I/O.
Runtime HarnessThe effectful layer: CLI, config, adapters, replay, judge calls, persistence, reports, and CI-exit mapping. Owns effects, not meaning.
EvalGlass SkillThe integration-time installer skill (discover / plan / install / re-vendor), now delivered as part of the EvalGlass plugin. Grants no authority; not needed at runtime.
Host-owned truthDatasets, references, rubrics, calibration, approved thresholds, baselines, host evaluators, and domain decisions — everything that confers authority.

Data spine

TermDefinition
TraceEnvelopeVendor-neutral normalized host behavior plus metadata, data policy, and provenance.
EvalUnitThe declared slice of behavior evaluated: call, step, trajectory, or session.
ExampleThe evaluator-ready item: input, output, unit, optional reference, context, metadata, provenance.
GoldHost-owned, validated reference data a reference metric compares against — never synthetic by default, never self-authorizing; only a host validation makes it gating-grade. (Marketing/trust pages say validated reference data instead.)
EvidenceBundleReferences, source material, judge evidence, verifier evidence, runtime errors, and trace fragments passed into the core.

Measurement & meaning

TermDefinition
MetricSpecA metric’s declared meaning: lens, score type, direction, profile, evidence needs, prerequisites, aggregation, threshold, authority, data policy.
Lens / Metric TypeWhether a metric is reference (compares to gold) or non_reference (inspects output alone).
ScoreOne metric result: value, status, validity, diagnostics, evidence refs, evaluator version, provenance.
ScoreBatchA set of related Scores emitted by one evaluator.
Score subject identityThe optional example_id/unit_id each Score carries (framework slice F1): which Example/EvalUnit it measured. Additive provenance, not meaning — it lets a reader group scores per call; it is never authority or source-function attribution.
DiagnosticStructured reason for a non-perfect state: code, severity, message, location, details, cause, evidence refs.

Trust & outcome

TermDefinition
AuthorityTyped inputs deciding whether a metric may gate: informational, blocked, or can_gate.
ProvenanceStructured run fingerprints recording how a run was produced, across ten dimensions.
Baseline comparabilityWhether two runs may be compared: comparable, not_comparable, missing_baseline, comparison_not_requested.
Data policyPer-source egress state: permitted, redacted, forbidden, missing, unknown — enforced before effects.
JudgeAn LLM-as-judge model whose evidence may gate only after host calibration.
Verdict EngineThe single path turning measurement and authority into a run outcome.
RunRecord / ScorecardThe complete machine record of a run / its machine-and-human summary, the primary artifacts.

Integration

TermDefinition
Port / AdapterA typed effect boundary / its concrete implementation. Adapters return evidence or data, never scores or verdicts.
Extension LaneAn opt-in, deletable integration attached through an existing port.
VendoringInstalling managed runtime source into a host repo under evals/_evalglass/. The skill copies only core/harness/adapters; the runtime then runs independently of the plugin and any agent.

Plugin surface

TermDefinition
/evalglass <verb>The umbrella the plugin exposes: setup, connect, run, view, explain, compare, baseline, ci (plus the v1.1 authoring verbs add-metric/add-judge/calibrate). Bare /evalglass is an honest status overview that runs nothing. There is no gate/approve/certify verb — the absence is the identity.
view granularitiesper-metric (default) · per-call (--by-call, grouped by Score subject identity, never list order) · per-source-function (advanced, not yet — needs a trace↔call-site correlation that does not exist).
Codex second runtimeEvalGlass also packages for Codex from the same canonical skills/ tree via a thin manifest; the vendored runtime is identical across runtimes. A public Codex marketplace listing is a maintainer step, not yet published.
Banned terms Never write kernel, test kernel, or pure kernel for the effect-free centre. Use Evaluation Core, effect-free core, or core isolation. Likewise, never describe a result as proven-correct, warranted, or endorsed — a Scorecard is a bounded claim, not a stamp of approval.

Confidence & decisions

EstimateA metric’s point value plus a confidence Interval and its effective sample size — not a bare number.
IntervalA named two-sided confidence band (wilson or student_t) with a level, lower, and upper.
n_effectiveThe count of eligible observations behind a point — the sample size a decision weighs.
Lower confidence bound (LCB)The conservative edge of the interval a default DecisionPolicy gates on, so a lucky small sample does not pass.
DecisionPolicyThe host-owned rule turning an Estimate into pass/fail/blocked; gates on the LCB by default; content-addressed.
Point-smoke policyA named policy that sets decision_statistic: point — the explicit dev escape hatch, never the silent default.
JudgeInstrumentThe content-addressed identity of a judge (provider, model, prompt/rubric digests); a change reads drifted.
JudgeAgreementStudyA computed, self-proving judge-vs-gold study (Cohen’s kappa recomputed from the confusion table).
AuthorityGrantA human approval bound to the SHA-256 of what it approved; edit the rig and it resolves mismatched.
ClaimSpecThe optional construct/validity argument for a metric’s interpretation; no gating power on its own.

Next steps