ito-inference

Topics in the source

• Itô Inference
• Current production boundary
• Required entitlement
• Future CLI and API contract
• Confirmation and execution gates
• Lifecycle and recovery
• Proposed backend stages

ito-inference is the sole canonical ECC skill for inference serving on Itô compute. Requests naming ito-serve route here; do not create or install a second ito-serve skill. ECC never SSHes to nodes, downloads weights, launches an engine, or exposes an endpoint; it never books, reserves, or spends. Managed serving is unavailable today. The ECC bridge exposes only login, auth, find, status, and explicitly gated evals. It has no serve verb. The canonical runtime documents inference only as an unsupported compatibility probe; ECC does not invoke or depend on it. The MCP surface exposes only auth, find, and status. The locally enforceable guarantee is that ECC rejects serve before resolving or spawning the credential-bearing canonical client. Therefore stop before authentication or any command invocation. Report the missing capability and return to the originating agent. Never substitute a local runner, SSH helper, browser workflow, purchase endpoint, or any untracked local ito-serve draft. When serving is implemented, its first gate is a server-verified completed booking. Harness memory, an RFQ, a quote, node IPs, or SSH access are not proof of entitlement. The backend must return fres

This is an excerpt. Refer to the complete source and its current requirements.