Explicit-requirement scenarios

Scenario workspace

Pick a reviewed scenario or name a class plus exact metric_id constraints. The filter reads the compact comparison index. A reported cell counts only with a canonical source id. It does not download landscape.json, fill a dash, query state=missing, or invent a comparison across units.

Loading the compact comparison data…

This workspace needs JavaScript to apply chips. Named scenario JSON, per-entity claim slices, and the query convention remain available without it.

scenario-views.json — reviewed explicit-requirement lists

Claim query convention — class, metric_id, state, evidence_grade

ET1 claim slice — filtered compare-index, including the published arm-load dash

Galbot G1 claim slice — wheeled mobile-manipulator claims only

Entity dossiers — per-identity JSON and HTML

What a scenario will not do

One membership class

Only subjects that already appear in that data-class enter the list. Wheeled Galbot G1 cannot enter a biped scenario.

Presence, not rank

Satisfying subjects have every required sourced cell. Values stay in authored units. There is no score and no best-robot order.

Gaps stay gaps

ET1 arm load is —. The miss list prints that dash. It is never rewritten as 0.

No org bridge

Shared affiliation does not transfer a claim. Boundary and superseded graph edges are excluded from any later stack walk.