How a challenge was played GM // OVERVIEW
Mode 1
Single Solve
Untimed. Start the challenge, receive the assigned artifact (or a live target for web challenges) and a list of questions, submit answers. The artifact is fixed for the attempt, so it can be fetched once and analysed at leisure.
Mode 2
Time Trial
Unlocked by a correct Single Solve. Same questions, but a freshly varied artifact per attempt and a short server-side deadline (often around thirty seconds). In practice only a solver that already works end to end can make it.
Mode 3
Mastery
Unlocked by a correct Time Trial. Several artifacts or targets at once (sets), each with its own copy of the questions, all due before one deadline. Answer identifiers carry a set prefix so each answer is tied to its artifact.
Start response GM // START
Starting a mode returned the contract for that attempt. The fields our solvers relied on:
- attempt_id
- Opaque identifier of this attempt. Repeating a start resumed the same attempt rather than creating a new one.
- answer_ids
- The exact keys the submit had to use, for example
message, or one key per field for multi-field challenges, orset2.messagefor Mastery. - questions
- One entry per answer id: the question text, a pointer to the artifact (or archive member) it is about, and an
answer_format. - answer_format
- A kind (
exact_text,pattern,enum,ordered_tokens,integer,json), a human-readable syntax, sometimes the allowed values, plus a normalisation note. - download / sha256
- A capability link for the assigned artifact and its hash, so the solver could prove it analysed the right bytes.
- targets
- For web challenges: the live target URL(s) assigned to the attempt instead of a file.
- deadline
- Present on timed attempts: the server-side cut-off. Submissions after it come back
expiredwith nothing graded. - run_for_time
- On newer timed routes, a flag that selects a ranked (Hall of Fame) attempt instead of regular play; older routes were timed by default and rejected the property.
Field contracts by mode GM // FIELDS
Single Solve example
answers:
message: "brisk-lantern-orbit-42"
One field (warmups) or many fields, each named by the question, for example a file size, a hash, a header offset or a configuration value.
Time Trial example
deadline: start + 30 s
answers:
message: "quiet-harbor-pine-07"
Same keys as the Single Solve, new bytes each attempt. Analysis, download and submit all had to fit inside the window.
Mastery example
answers:
set1.message: "amber-signal-drift-11"
set2.message: "cold-meadow-relay-58"
set3.message: "north-cipher-gate-23"
Several artifacts (or several web targets, answered as proof-1, proof-2 ...) under one deadline.
Results and refusals GM // CODES
Submit results
- CORRECT
- Mode completed; the response carried the completion token for the mode.
- accepted
- Some fields accepted, with a count of how many remain.
- incorrect
- Nothing awarded. A batch with any wrong field was rejected as a whole, without saying which field.
- expired
- The timed window had closed; nothing was graded.
Conflicts we learned to read
- prerequisite_required
- An earlier mode is not CORRECT yet (Mastery before Time Trial).
- timed_intent_not_available
- The single ranked attempt is already spent, or the route is an older one that does not accept the ranked flag at all.
- retry_variants_unavailable
- No untimed variants left for a retry or practice run.
- start_required
- Status asked before starting; the response still included the public question contract, which let us prepare without opening a window.
Status probe example
op=status example-lane-day-00/time_trial
-> result: "expired"
unique_attempts_remaining: 12
A free status call reported how many attempt variants remained on a route. Reading it before opening a timed window was one of the cheapest protections we added: a zero meant the next attempt was the only one.