Red Shell · Common Errors

All mistakes/Section 1: The Foundations Every Task Must Get Right

1.2The task relies on records the universe does not hold

Fails the taskTrajectory - Feasibility With Tools

The mistake

A rule reads off records the assigned universe does not hold, such as a catalog or a policy page, while prompts, inputs and criteria read as if they were there.

Do this instead

Before the run, query the universe once per rule and rewrite any rule whose record is missing. If it only surfaces in Leg B, redesign the task rather than hint again.

Where it happened

One real task. 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 2Commerce & Product · 3 Leg A turns

What is wrongpantry_rules.md prices every line from Fresh's catalog and the delivery fee from Fresh's Delivery Policy. The universe's catalog holds none of the five board items, and its policies are empty.

Leg A turn 1 asks Model A to check the five listings on Tom's pantry_board_draft.png and work out what each apartment owes, under the house rules in pantry_rules.md.

Where it shows

…For the delivery fee we go by Fresh's Delivery Policy and nothing else…rule 5
…if the search is coming back empty try getting to the product pages and the policy pages another way…the hint the missing records forced
…the two endpoints that serve product pages and policy text (search_shop_catalog and search_shop_policies_and_faqs) return zero results for everything…

What it should have been

Before prompt 1
Search the universe's catalog for the five items, and its policies for the fee. Both come back empty, so the rules change before the run.
Rules 1 and 5 cite only records the universe returns.

How it breaks the standardPricing every card and what each apartment owes rests on rules 1 and 5, so neither Model A nor Model B can do the main request. The golden keeps Tom's board prices, flagged unconfirmed, and criteria 16, 17 and 26 want Fresh's $0.55 a lb bananas, $5.45 spinach and $4.99 fee, which no tool returns.

The rule it breaksGuidelines · 1.2.1 Start With the Universe The universe combined with the multimodal input has to sustain the opening prompt and every follow-up you intend to add

Catch it in your own task

Your golden shows it: an empty search, a Leg B hint sending Model B another way, figures flagged as unconfirmed.

Where the correct guidance is written

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

Guidelines · 1.2.1 Start With the Universe

The universe combined with the multimodal input has to sustain the opening prompt and every follow-up you intend to add

Guidelines · 4. Valid vs. Invalid Model Failures

Data that is not in the server, asked for anyway, and the model penalised for not finding it.

Listed under “Not valid: your defect, or the platform's”.

1 more source

QC spec · Trajectory - Feasibility With Tools

The primary request is impractical or impossible and can't be answered by the tools available or enabled for the task.

Fails the task when the missing records carry the main request; costs points otherwise.

Why it matters

A rule pointing at data no tool returns cannot be followed by any run, so every criterion downstream of it is unreachable. Not wrong. Impossible. It takes the difficulty with it too: if that data was the second system the task cross checks against, every cross check has nothing on the other side, and the task is no longer multi system.

Every example taken apart, with the task, how it breaks the standard and what it should have been: 1.2 The task relies on records the universe does not hold, in the explanations →