Red Shell · Common Errors

All mistakes/Section 3: Milestones

3.2Stopping rules that do not gate the turn

Costs pointsMilestones - Continuation Criteria & Assets · Milestones - Milestone Annotations

The mistake

Continuation criteria, read in Leg B to decide when Model B moves on, either miss one of their Leg A turn's asks or demand what that turn cannot produce, such as a later turn's file.

Do this instead

Tick every ask in each Leg A prompt against a clause, and move any clause that needs a later file or ask to the turn that brings it.

Where it happened

2 real tasks. Each shows the spot and what it should have been; click any line to open the task there.

the words at faultthe row or field at faultmissing from the taskwhat is righta task file

Example 10Small Business & Personal Docs · 4 Leg A turns

What is wrongMilestone 8, on Leg A turn 2, requires the travel rules in IMG_0819_travel_policy.jpg, which only Leg A turn 3 hands over. Milestone 9 repeats its intent there, word for word.

Leg A turn 2 hands over IMG_0814_calendar.jpg and sets the travel itself: “about three days a week”. The travel directives, IMG_0819_travel_policy.jpg, arrive at Leg A turn 3.

Where it shows

Milestone 8Leg A turn2
The user has sent the travel rules his employer issued and wants the schedule rebuilt… the travel days in the model reflect only the document the user attached, with no residual figures from a prior assumed pattern

What it should have been

Milestone 8Delete it
milestone 9, on Leg A turn 3, already carries it

How it breaks the standardAt Leg A turn 2 the only file handed over is the calendar, and the user sets the travel at about three days a week himself. No correct response to Leg A turn 2 can meet the clause, so in Leg B it would keep you hinting Model B toward a directive not yet handed over.

The rule it breaksGuidelines · 6.2 Writing the Milestones Write one clause per requirement of that turn That turn is the milestone's Leg A turn.

Example 11Visual Learning · 4 Leg A turns

What is wrongLeg A turn 1 asks which pieces still carry a correction, and none of milestone 1's six clauses checks it, so Model B can pass milestone 1 without it.

Leg A turn 1 asks, among other things, which pieces still carry a correction. None of its three exports does, and Slack holds corrections for pieces outside the drop.

Where it shows

No clause checks which pieces still carry a correction.

What it should have been

Milestone 1Leg A turn1
Each card states whether its piece still carries a correctiona seventh clause, beside the six it has

How it breaks the standardIn Leg B you move Model B past milestone 1 once its six clauses hold, and a response that never checks corrections meets every one. Here the right answer is none of the three, so a response that skips the check, or pins another piece's Slack correction on one, moves on unchecked. This costs points.

The rule it breaksQC spec · Milestones - Continuation Criteria & Assets they would let the simulator advance while a requirement of that turn is still unmet In Leg B, the simulator is you.

Catch it in your own task

Could a response skip one of the Leg A turn's asks and still pass? Could a correct one fail for lack of a later file?

Where the correct guidance is written

Section titles as they print, so you can search for them in the document.

Guidelines · 6.2 Writing the Milestones

Write one clause per requirement of that turn, separated by pipes, each of them true or false on inspection.

That turn is the milestone's Leg A turn.

QC spec · Milestones - Continuation Criteria & Assets

Continuation criteria are present and checkable but under-specified — they would let the simulator advance while a requirement of that turn is still unmet.

In Leg B, the simulator is you.

Why it matters

In Leg B you are the simulator, and continuation criteria are what you advance on: once Model B's response meets them you move to the next milestone, and until it does you send another hint. A missing clause lets Leg B move on with a requirement unmet, and every later turn builds on the hole. A clause the turn cannot satisfy does the opposite: it keeps you hinting Model B toward something the user has not handed over yet.

Every example taken apart, with the task, how it breaks the standard and what it should have been: 3.2 Stopping rules that do not gate the turn, in the explanations →