Public docs
Use this layer to understand what YAI is now: local-first, online-authorized, account-backed, case and evidence oriented, runtime and client based, and prepared for future release and access integration without pretending those integrations already exist.
Hub
| Topic | Primary route | What it explains now | What it does not claim |
|---|---|---|---|
| Runtime model | Get Started | Explains the local-first runtime path and how source, account and case work relate. | Not a finished install guide, hosted platform walkthrough or release-backed runtime package. |
| Account and YAI Home | Account / YAI Home | Shows create-account-first entry and the future signed-in product home without fake account or plan state. | Not live auth, active Open Preview assignment, Preview Plan assignment or loaded YAI Home projections. |
| Download and release access | Download | Separates source visibility, future packaged releases, future eligibility and runtime authorization. | Not a Download Now surface, artifact catalog, installer index or live release gate. |
| Interfaces and clients | Interfaces | Frames CLI, Loom and VS Code as runtime-attached clients rather than product authority surfaces. | Not a hosted console, release package list or live capability matrix. |
| Governed action patterns | Patterns | Explains case-centered work, evidence, reviewability and serious automation beyond chat transcripts. | Not customer case studies, production metrics or live automation telemetry. |
| Deploy and local-first operation | Deploy | Explains local-first runtime posture, online authorization and the account-machine-license boundary at a high level. | Not a finished deploy pipeline, environment recipe, command runbook or hosted setup guide. |
| SDK and integration boundary | SDK | Explains contract consumers, clients, auth context and runtime gate boundaries without claiming public package maturity. | Not an installable package index, generated client catalog or API reference. |
| White Paper and doctrine | White Paper | Carries the doctrine, architecture stance and product problem behind governed software action. | Not a polished publication PDF, pricing narrative or launch brochure. |
| Questions and answers | Q&A | Gives short answers about account entry, YAI Home, download posture and runtime boundaries. | Not a support desk, release bulletin, live account console or launch FAQ. |
Public now
This is a public documentation layer, not the final operator manual for a finished platform. It packages the current story across runtime, account entry, download, clients, doctrine and readiness so the public routes describe the same system model.
Use Status for readiness, Account for create-account-first entry, Download for release-access structure, Interfaces for clients and YAI Home for the future signed-in home on the technical `/dashboard` route.
Public site
The public site explains the product surface and keeps the routes aligned without pretending to be the runtime or the account system.
Account and release
Account creation, sign-in, account posture and release decisions belong to the account and release platform, not to this docs route.
Runtime and clients
The runtime and its clients remain the place where execution, authorization and governed work actually happen.
Cross-links