PASS dashboard is observer/proxy and canonical worlds live in three different processes
PASS A discovers C transitively from local bridge knowledge without dashboard topology
PASS C still starts Open Null and finite query materializes one demanded node
PASS A autonomously routes A→B→C with per-hop bridge transforms
PASS route and federation continue after dashboard process is stopped
PASS when B disappears A and C negotiate a direct task-local federation
PASS task-local capability negotiation can be denied by target local policy
PASS duality transport remains non-commuting under decentralized routing
PASS A coordinates transaction locally; dashboard owns no proposal state
PASS stale proposal is rejected only by B after B mutates
PASS coordination debt persists on A across A process restart and can reconcile
PASS B canonical state remains persistent across actual process restart
