Get Started
Get Started
Start from real surfaces only. Source visibility, client access and runtime operation stay separate until account plan posture, entitlement limits and future machine authorization exist. Provider/model and hosted actions remain future governed capability.
Runtime path
Entry table
| Stage | Surface | Current state | Operation requirement | Link |
|---|---|---|---|---|
| Source | Public repository | source where public | does not grant runtime operation | GitHub |
| Runtime | Runtime / System | not published | account plan and entitlement posture required later | Runtime catalog |
| Clients | CLI, Loom and VS Code | planned surfaces | attach through governed runtime posture | Interfaces |
| Account | Open Preview account posture | Preview Plan is the default initial account plan model | auth, entitlement limits and machine posture may be required before governed operation | Account |
| Case work | YAI Home, case://user and nested cases | target model | principal, account, case and future machine posture may be required | Open YAI Home |
No production setup guide, artifact flow, live account authorization, billing flow, offline-use guarantee, fake command transcript, runtime state, hosted execution, provider budget, model access, team workspace, admin control or target command is presented here.