Q&A
Questions and answers.
A compact public Q&A for the account entry surface, YAI Home label, download posture and runtime boundary.
Public Q&A
Short answers to the common questions
- Is YAI a hosted SaaS dashboard?
- No. The public site is the front door. The product model stays local-first and online-authorized, with runtime and client behavior kept separate from the website.
- Does creating an account unlock access right now?
- No. Account entry exists, but real account creation, sign-in, session state and account posture still depend on the account platform.
- Can I download a packaged release today?
- Only when Download is backed by real release data. The current page explains the structure without inventing artifacts, versions or checksums.
- Is YAI Home the same as /dashboard?
- YAI Home is the product label. /dashboard remains the technical route that will carry the signed-in shell when real account and product data exist.
- Are Google or Apple sign-in available?
- Not in the current public account flow. Email and password is the first account method shown on the website.
Related routes
Go to the underlying surface
DocsPublic docs hub for runtime, account, download and doctrine.AccountCreate-account-first email/password entry surface.DownloadSource visibility, future release access and runtime boundary.StatusPublic readiness surface rather than live monitoring.White PaperDoctrine and architecture behind the runtime model.InterfacesCLI, Loom and VS Code as client surfaces.