CGOD is a small dispatcher. Each agent publishes a manifest of what it can do and how busy it is. A short JSON policy says who may take which task. When a task comes in, the daemon checks every agent against the policy, assigns the best eligible one, and escalates to the next one if the first times out.
The demo below runs the matching and escalation logic in your browser on example manifests for the fleet's five agents. Capabilities and load figures are invented for illustration.
| Agent | Host | Capabilities | Load | Decision |
|---|
A manifest file per agent (capabilities, limits, owner) checked into the fleet repo, a heartbeat that reports current load, and this matcher running inside the existing hub on port 8899 instead of as a separate daemon. Start with a plain CLI (cgod submit, cgod status) and an append-only log. Capability "verification" can begin as a short smoke test each agent must pass before a capability is listed.
max_load to 0.9 in the policy and resolve again; a busier agent becomes eligible."deny": ["Muse"] to a rule and see the trace mark it as blocked by policy.