Speculative drafting

After grading, a reviewer model reads the submission's files and the agent's trajectory and checks each of the task's rules. A failed check makes the score 0. Step numbers link into the trajectory.

LLM adversarial review is not proof of arbitrary program behavior. Host storage and task-specific deterministic checks remain required.

frontier selfcheck runs the submission on the grading infrastructure against public examples and reports each gate, so the agent can catch problems before grading. Each run gets four. This agent used 2 of 4.

1. 1
   passed8h 0m into the runtook 2m 6s

   startup 29.6 s of 300 s; 2/2 gates passed; The serving gate was projected from a sample: 76-token windows, spread from openings to ends, of the first 32 of the 40 public conversations (2,432 of the held-out set's 44,314 continuation tokens), walked under the budget scaled to them (593 s).

   7 gates

   • ✓review prerequisites
   • ✓submission size
   • ✓startup · GET /health answered 200 after 29.6 s
   • ✓POST /draft · {"draft": [2528, 11, 9669, 717, 3658, 8402, 18670, 4698, 1639, 11, 15, 62, 21, 15, 17242, 11]}
   • ✓held-out serving time (projected) · projected from 496 of about 9,038 held-out requests at concurrency 32: 34.0 s of serving over 36 rounds for 2,432 public continuation tokens, scaled to the held-out set's 44,314 as validate.py does, plus the smoke request's 0.3 s once; within about 10% of the held-out serving time: a few percent high for a server that answers requests one at a time, up to 10% low for one that batches the requests in flight
   • ✓request failures · 0 of 496 requests failed, timed out or were malformed; each scores as an empty draft
   • ✓healthy after requests
2. 2
   passed10h 17m into the runtook 2m 4s

   startup 31.4 s of 300 s; 2/2 gates passed; The serving gate was projected from a sample: 76-token windows, spread from openings to ends, of the first 32 of the 40 public conversations (2,432 of the held-out set's 44,314 continuation tokens), walked under the budget scaled to them (593 s).

   7 gates

   • ✓review prerequisites
   • ✓submission size
   • ✓startup · GET /health answered 200 after 31.4 s
   • ✓POST /draft · {"draft": [2528, 11, 9669, 717, 3658, 8402, 18670, 4698, 1639, 11, 15, 62, 21, 15, 17242, 11]}
   • ✓held-out serving time (projected) · projected from 494 of about 9,001 held-out requests at concurrency 32: 34.6 s of serving over 32 rounds for 2,432 public continuation tokens, scaled to the held-out set's 44,314 as validate.py does, plus the smoke request's 0.4 s once; within about 10% of the held-out serving time: a few percent high for a server that answers requests one at a time, up to 10% low for one that batches the requests in flight
   • ✓request failures · 0 of 494 requests failed, timed out or were malformed; each scores as an empty draft
   • ✓healthy after requests

The agent's last message before its session ended.