Yellowstone Simulation Status

Couplings within and across domains

Each node is a simulated component in its domain's cluster; each line is a physical or ecological quantity one component passes to another.

Components by domain and status

Counts per domain. Click a cell to show that domain on the map.

Couplings between domains

Rows feed columns; off-diagonal cells cross domains. ▲ counts couplings that are partial or missing. Hover a cell to list them.

Fixes queue, verified per item

One bar per fixes document, grouped by the code area that owns it. Counts come from the ledger rows, which are updated as items land; new audit documents count every finding as open until they get a ledger.

What the Godot world draws

Each Godot system, its state, and the Python components that drive it.

All components

The table view of the map. Search by name, domain, state or method.

Refresh after fixes land: python3 dashboard/build_data.py from the project root, then reload. Sources: dashboard/data/inventory-*.json (component and coupling evidence, file:line) and yellowstone_python_spec/fixes/ledger/ (per-item verdicts). dashboard/data/node-map.json links Godot systems to the Python components that drive them.