Terminal client
YAI CLI
Terminal and operator interface for local runtime inspection, command surfaces and case-aware workflows without owning account plan, entitlement, source, artifact or release authority.
Interfaces
Interfaces attach to the runtime. They do not own it.
CLI, Loom and VS Code are client surfaces for observing, inspecting and operating the governed local-first runtime. Source or future release access can exist separately from account plan, entitlement-governed capability, release/update and future machine authorization decisions.
Operator shell
YAI Loom
Visual operator shell for runtime visibility, review loops and controlled interaction with governed work while external services may later coordinate account plan, provider/model and entitlement-governed capability decisions.
Editor client
YAI for VS Code
Editor-side client for case-bound development workflows without moving runtime truth, account state, release eligibility, machine posture, repository visibility or commercial authority into the editor.
Client model
Clients attach, inspect and operate.
- Runtime truth stays in the governed runtime.
- Clients do not own identity or case state.
- Governance, evidence and records remain runtime-bound.
- Client source visibility, clone access or future client release access does not equal governed operational authorization.
- Account plan, entitlement, release, update and machine authorization decisions stay external to these clients; interfaces do not authorize trusted runtime machines themselves.
- Online authorization may gate future capabilities without making clients the source of authority.
- Local-first work can still depend on account-linked authorization, Preview Plan posture and entitlement limits when preview services exist.
- Future platform policy can later affect providers, models, releases, organization posture and interface actions without turning clients into account, hosted compute, admin or model-authority surfaces.
- Clients may later display safe access reasons for provider/model, hosted or organization-managed capability, but policy decisions still come from external authorization work.
- Preview Plan posture, entitlement limits or higher-access review posture may later affect what these clients can reach without turning them into review surfaces.
- Clients may later respect runtime update posture or minimum-compatibility policy without becoming update-control surfaces.