The agent roster is two GETs

Your coordinator needs to know which agents exist tonight. In a framework, that answer lives in a registry you maintain: a config file, a graph definition, a list that drifts.

On Hoody, the coordinator calls GET /api/v1/agent/realms, picks a realm, then GET /api/v1/agent/containers?realm= and receives every agent container in it: name, status, and the endpoint to bind a session to. Spin up three more worker containers and the next GET returns three more rows. Retire one and it leaves the roster by leaving the realm.

The orchestration framework's central promise was knowing who's available and how to reach them. The platform already knows, because the agents live in it.