UnifiedFlow Worker Admission and Capability Routing
This is a queued continuation lab for the UnifiedFlow data-center platform. It exists so the overview lab can stay focused on the whole system while this subsystem gets its own evidence, figures, and update loop.
Research Question
How does UnifiedFlow decide that a physical or remote machine is allowed to carry scientific work?
Current Evidence
Current evidence includes the worker lifecycle model, Biscotti operating identifiers, heartbeat expectations, resource visibility, and capability-based scheduling notes.
Platform Use
This lab should define the admission contract: what a worker must prove, how its resource class is advertised, how leases are bounded, and when it should be drained or quarantined.
Desired Outcome
Scientific jobs route to trustworthy capacity because machines are promoted through evidence and policy, not by convenience or name alone.
Continuation Work
Turn the worker lifecycle into a state table with required evidence, failure modes, and operator actions for each state.
Starting Figure Obligation
This lab needs at least one subsystem figure promoted from evidence: a state machine, network, hierarchy, matrix, or time-series chart depending on the subsystem. The figure should make the operating decision inspectable, not merely decorate the page.
Claim Boundary
This page is a draft queue item. It should not be treated as a final scientific or operational claim until evidence links, figures, and review-state decisions are added.