Compute orchestrationInfrastructure
Target registry
Describe local and cloud targets, identity, capabilities, cleanup policy, and admission state in canonical registry entries.
Target registry — contract and behavior
- Operators publish their registry from the example schema; runtime never treats an arbitrary discovered host as trusted capacity.
- Local host identity must uniquely match before destructive cleanup or remote bootstrap is allowed.
- Registry commands inspect and maintain target records without rewriting queue history.
- Capabilities and admission state guide scheduling but do not substitute for live capacity broadcasts.