Core developers
Versioned Core protocols
Clients use versioned contracts to ask a selected Core for specific observations or actions. A published wire format describes what to send. The carrier and the destination determine who may send it.
Select the carrier
| Contract | Endpoint and scope |
|---|---|
| Foundation status | Bodyless GET /v1/status on the owner-private Unix socket. Send Accept: application/vnd.cleetus.host+json;version=1. The reply identifies the Host, instance, platform, expiry and observed capabilities. |
| Task readiness | GET /v1/inspection/task-readiness on the reviewed local inspection endpoint. The v1 task-readiness media type returns one workspace and board revision with outstanding dependency counts. |
| Routed graph | POST /v1/inspection/routed-execution-graph on the gateway's authenticated private socket. The v1 request names both the gateway and the exporting Core by Host and instance ID. Both sides require a reviewed graph route. |
| Paired catalog | GET /v2/mesh/hosts over paired, pinned HTTPS with X-Cleetus-Version: 2 and the paired session bearer. The catalog supplies the target coordinates used by the separate, typed mesh read. |
Decode a local status read
cleetus-host inspect status
The native CLI discovers the installed service under the current OS account and checks socket custody and peer identity. In a client, reject a mismatched Host, an expired observation or an unsupported version. Use the returned instance to bind subsequent reads. Preserve unknown values in displays and handle a replacement instance as a new runtime.
Extend a contract
Keep public values and bounded codecs in the pure protocol package. Add a typed operation to the responsible owner, verify it at the authenticated carrier and publish its limits. A cross-host request that loses its acknowledgement must retain the destination and original operation ID for reconciliation. Module ownership · Agent mesh