Scenarios

Explicit-requirement scenarios

Ask which subjects in one class have explicit sourced cells. The result is a presence list, not a ranking.

Limits of the list

Distinct payload definitions stay distinct. Organization nodes are not a compatibility bridge. A dash is a published gap, never zero.

Scenario workspace

Pick a reviewed scenario or name a class plus exact metric_id constraints.

How the filter works

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…

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 first

Satisfying subjects have every required sourced cell. Values stay in authored units. Ranked fit scores build on this list; see Scores and Sim readiness.

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.