Daily

Daily Lab · recorded replay · run 008af826 · clean

positional-v0

Rejected

universal-refusal: 0/48 cases satisfied, threshold 1Under the current criteria, generation 2. This run faced generation 1 when it executed — both verdicts are below.

Historical behaviour: associates results[i] with articles[i] and pads the tail. This is what production does today.

01

Verdict

2 criteria generations

Criteria generation

spec f027762ab4d08b35

Rejected

universal-refusal: 0/48 cases satisfied, threshold 1

Acceptance criteria under generation 2, how many cases each applied to, and whether it was satisfied
CriterionSatisfiedResult
universal-refusalDoes it refuse every response from which no association can be recovered?0/48not met
association-exactOn its own protocol, does every article receive exactly the verdict it was given?0/3not met
protocol-violation-refusalDoes it refuse duplicate, unknown, missing ids and unusable scores?0/1not met
no-crashDoes it terminate on every case without crashing or hanging?52/52met
complete-evidenceIs there a prediction record for every applicable case?52/52met
protocol-exclusivityOn cases outside its declared protocol, does it refuse rather than associate anyway?0/12not met

Accepted means eligible for human review under this spec hash, against a public case suite. It is not evidence of production quality, and it does not establish generalisation: the cases are visible and a candidate may have been written against them.

03

The patch

against positional_v0.py

This run is the baseline itself, so there is nothing to diff against.

Reproduce this run

cd backend
EVAL_OFFLINE=1 venv/bin/python -m lab.orchestrate \
  --candidate positional-v0 --tag clean
cd ../web && npm run export:lab -- --check

Source under test

backend/lab/contract/versions/positional_v0.pysha256 d6f155ab7bcf0b89… · 3795 bytestranscribed from origin/main:backend/app/services/openai_service.py

04

Timeline

1 attempt
  1. 01succeededcompleted 64 cases in 33.7mslocal-known · started 2026-09-22T19:47:57.443Z · ended 2026-09-22T19:47:57.478Z

Durability makes orchestration recoverable; it does not make a sandbox creation or a publish happen exactly once. An attempt the orchestrator never saw finish is recorded as unknown-outcome rather than assumed to have failed.

05

Cases

52 scored, 12 not applicable
Recorded cases
42real batches, replayed
Fault-injected
10labelled synthetic
Correct
0of the scored cases
Wrong
52see the table
Every case this candidate got wrong
CaseGroupWhat happenedWhy it is wrong
observed-2026-09-02-000observedshould-have-refused27 verdicts recorded for 40 articles
observed-2026-09-02-001observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-002observedshould-have-refused18 verdicts recorded for 20 articles
observed-2026-09-02-003observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-004observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-005observedwrong-associationno ground truth recorded
observed-2026-09-02-006observedshould-have-refused201 verdicts recorded for 40 articles
observed-2026-09-02-007observedshould-have-refused33 verdicts recorded for 40 articles
observed-2026-09-02-008observedshould-have-refused37 verdicts recorded for 40 articles
observed-2026-09-02-009observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-010observedshould-have-refused19 verdicts recorded for 20 articles
observed-2026-09-02-011observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-012observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-013observedshould-have-refused25 verdicts recorded for 40 articles
observed-2026-09-02-014observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-015observedshould-have-refused19 verdicts recorded for 20 articles
observed-2026-09-02-016observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-017observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-018observedshould-have-refused59 verdicts recorded for 40 articles
observed-2026-09-02-019observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-020observedshould-have-refused19 verdicts recorded for 20 articles
observed-2026-09-02-021observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-022observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-023observedshould-have-refused36 verdicts recorded for 40 articles
observed-2026-09-02-024observedshould-have-refused21 verdicts recorded for 20 articles
observed-2026-09-02-025observedshould-have-refused31 verdicts recorded for 40 articles
observed-2026-09-02-026observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-027observedshould-have-refused19 verdicts recorded for 20 articles
observed-2026-09-02-028observedshould-have-refused38 verdicts recorded for 40 articles
observed-2026-09-02-029observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-030observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-031observedshould-have-refused31 verdicts recorded for 40 articles
observed-2026-09-02-032observedshould-have-refused53 verdicts recorded for 40 articles
observed-2026-09-02-033observedshould-have-refused19 verdicts recorded for 20 articles
observed-2026-09-02-034observedshould-have-refused34 verdicts recorded for 40 articles
observed-2026-09-02-035observedwrong-associationno ground truth recorded
observed-2026-09-02-036observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-037observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-038observedshould-have-refusedcompletion stopped for 'length'
observed-2026-09-02-039observedshould-have-refused25 verdicts recorded for 40 articles

Showing the first 40 of 52. The full set is in the artifact below.

06

Unscored

Measured, and deliberately not graded

A criterion decides; a diagnostic reports. Promoting one of these to a criterion would change the spec hash and re-decide runs that never faced it, so a gap found after the fact is published as a number rather than closed behind your back.

12/12

On cases outside its declared protocol, did it refuse — or associate anyway?

It produced a complete association on 12 case(s) outside its declared protocol. Under this generation that fails protocol-exclusivity; under generation 1 it was not graded at all.

syn-keyed-in-order, syn-keyed-reversed, syn-keyed-rotated, syn-duplicate-id, syn-unknown-id, syn-missing-id, syn-score-nan, syn-score-out-of-range, syn-score-string, syn-score-null, syn-relevant-not-bool, syn-empty-results

07

Provenance

What can and cannot be established
Executed at revision
4e8bee7625820107e84184f8e24c6bd7125f2e86+dirtyrecorded when the harness ran, not re-derived at export
Inputs sha256
a60d5a6ac6d7050dcases, records, candidates and event logs
Evaluator sha256
277ec81521ba14d8
Spec hash
f027762ab4d08b35
Execution mode
offline-replayThe harness reads committed responses from disk and makes no network call. The candidate imports nothing beyond the standard library.
Python
3.12.13
Model calls
0
Spend for this run
$0Offline replay of committed recordings: no inference call was made, so provider spend for this run is $0. What the original recordings cost is not attributed per batch anywhere in this repository, so it is left unknown rather than estimated.
Recording cost
unknown
Sandbox limits
python3.13, network disabled120s wall clock, none secrets. This candidate matched a committed implementation, so it ran locally and the boundary was not exercised here.

Case suites

backend/lab/cases/observed.json42 cases · sha256 3d7f4b4143d85ab3backend/evals/.cache/llm via offline replay

backend/lab/cases/synthetic.json22 cases · sha256 21c92da332a9837elab/build_synthetic.py — fault injection, ground truth by construction

  • Note. Every case ran offline against responses already committed to this repository. No inference call was made and no provider was charged.backend/evals/.cache/llm
  • Caution. The case suite is public. A candidate may have been written against it, so passing does not establish generalisation.backend/lab/cases/
The full artifact, as published

Validated against the schema in web/lib/lab/artifact.ts before it was written. Download the JSON.