ito-training

Topics in the source

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

ito-training is the canonical ECC skill for training on Itô compute. ECC never runs a trainer, scheduler, or data pipeline of its own; it never books, reserves, or spends. This skill chains off a completed booking from ito-compute. Managed training is unavailable today. The ECC bridge exposes only login, logout, auth, find, status, and explicitly gated evals. It has no train verb, and the canonical CLI's run verb and desk training-run backend remain scaffolds. The locally enforceable guarantee is that ECC rejects train 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 trainer, SSH helper, browser workflow, or purchase endpoint. When training 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 fresh training eligibility bound to the authenticated account, booking, GPU topology, region, fabric, and term. Expired, revoked, mismatched, incomplete, or already-released bookings fail clos

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