Status and readiness
This page explains what is publicly available now, what is prepared but not connected, and what depends on the account platform or the runtime layer.
Status is framed here as public readiness, not live uptime monitoring. No incident feed, uptime percentage, API monitor, release channel monitor, account-state monitor or runtime telemetry feed is claimed by this page.
Matrix
| Surface | Current public state | Where live state comes from | What this page does not claim |
|---|---|---|---|
| Public website | Static public routes are available as website surfaces for account entry, download, interfaces, docs and legal context. | Website layer | Not a live uptime SLA, incident feed, provider monitor or mature SaaS operations console. |
| Account entry | Create-account-first email/password UI exists on /account as a public entry surface. | Account platform | Does not claim real account creation, credential validation, session issuance or fake user state. |
| Sign in entry | Email/password sign-in entry exists as a shell-level surface. Google and Apple remain deferred. | Account platform | Does not claim live sign-in success, session state, Open Preview state or Preview Plan assignment. |
| Signed-in product shell | The technical /dashboard route exists as the future signed-in product shell and destination. | Account platform + runtime layer | Does not claim live product-home state, account-safe projections, release state or runtime state. |
| Download surface | The public Download page exists and separates source visibility, release packaging, account eligibility and runtime authorization. | Website now; release services later | Does not claim artifacts, versions, checksums, release dates, Download Now actions or account-gated download state. |
| Release packages | Release package structure is prepared conceptually for future website/release contracts. | Release services | Does not claim live release channels, eligibility decisions, assigned packages or artifact availability. |
| Runtime authorization | Runtime/client authorization is explained as a separate readiness boundary from website, account entry and download access. | Runtime layer | Does not claim live runtime health, machine authorization, license lease state or gate decisions. |
| Legal / pre-release context | Privacy, Terms and Pre-release context remain public reference routes supporting the current website boundary. | Website layer | Does not claim commercial launch status, billing readiness or mature production operations monitoring. |
Alignment
Account readiness follows the current account-entry model: email/password is the first account method, Account is create-account-first and Sign in remains a truthful entry surface without fake session state.
Download keeps source / clone, future release packages, future account eligibility and runtime authorization separate.
The signed-in product shell remains on the technical /dashboard route. Runtime and client operation remain separately governed after install or account entry.
Website layer
The status page can describe public readiness and route structure, but it does not stand in for live operational monitoring.
Account and release
Account state and release decisions come from the account and release layer later, not from static website copy.
Runtime layer
Runtime operation, authorization and machine or license use stay with the runtime layer even after account and release data exist.
Privacy, Terms and Pre-release context remain supporting public reference routes, not evidence of commercial launch, live service health or mature production monitoring.
Use Privacy, Terms and Pre-release context for the current public boundary, not for live system-state claims.