Deploy posture
Deploy posture for a local-first, online-authorized runtime.
Deployment is framed here as where governed runtime operation lives and how later account, machine and license boundaries surround it. This is posture only, not a finished deploy pipeline.
Posture
What deployment means on the public surface
YAI is local-first. The runtime belongs near the machine and the work, while online authorization remains a separate boundary around operation. That split matters because source visibility, account posture, release access and runtime use are related but not identical.
The public site can explain the posture before real packaged releases, account-safe projections or runtime gate consumption are connected. That is the current role of this route.
Boundary map
Current deploy boundary
| Surface | Current public meaning | Where live state comes from | What this route does not claim |
|---|---|---|---|
| Local runtime placement | Operation stays near the machine and near the work instead of being described as a browser-only control plane. | Runtime layer | Not a hosted-only platform, managed control plane or finished deployment topology. |
| Online authorization | Account-backed authorization remains separate from local execution so operation can stay governed without turning the website into the runtime. | Account platform + runtime layer | Not offline-first, not permanent disconnected authority and not live auth_context issuance from this route. |
| Account, machine and license boundary | Account posture, later machine posture and later license posture are distinct layers around runtime use. | Account platform for state, runtime layer for use | Not live machine authorization, license lease state, runtime seal state or entitlement evaluation. |
| Source and release distinction | Public source visibility can exist separately from future packaged release access and separately again from runtime authorization. | Public site now; release services later | Not repo URLs, installer names, package versions, checksums or release dates. |
| Deploy surface | This route explains posture and boundaries so operators understand what deployment means in YAI before real release contracts arrive. | Public docs layer | Not a finished deploy runbook, environment recipe, infrastructure template or command catalog. |
Non-claims
What this route intentionally does not publish
- No fake install or deployment commands.
- No fake infrastructure topology or hosted runtime guarantee.
- No fake installer, artifact, checksum, version or release date.
- No fake machine authorization or license lease state.
For runtime orientation use Get Started. For release-access structure use Download. For readiness use Status.