VIS-ALPHA-01PRIVATE DEVELOPMENT ALPHA / NOT A RELEASEProduct map
Inside the AlexOS Development Alpha
Five destinations give the local application a legible shape: Today for orientation, Workshop for governed conversation, Journal for deliberate source selection, Library for eligible recall, and More for evidence and control surfaces.
Governing rule
A visible capability is not the same as production authority.
Context
AlexOS is being developed as a local-first desktop environment rather than a general chat wrapper. Its current navigation separates immediate orientation, active work, source selection, retained material, and institutional controls so those responsibilities do not collapse into one interface.
Current state
The five-destination shell and bounded native workflows exist in the private Tauri, React, Rust, and SQLite development alpha. The system remains locally operated and evidence-gated; broader distribution, automatic model routing, and production authority have not been granted.
Current evidence
What the record supports.
Primary destinations
5
Current Workshop identity
RC9
Cloud fallback
None
Distribution
Private local alpha
Production release
Not authorized
Today provides a quiet entrance, exact thread continuation, dismissal, and a synthetic Try path
Workshop hosts governed conversations while the recorded RC9 identity remains active
Journal supports deliberate source selection with approval-time revalidation
Library searches eligible substance while excluding revoked or changed sources
More groups history, evidence, founder, administrative, and control surfaces behind their recorded gates
Public evidence files
Inspect the record.
Public-safe derivatives only. Source availability does not broaden the claim stated on this page.
Application screenshotsExact-screen privacy, state, and release review remains incompleteWithheld
Private application sourceImplementation-sensitive code is outside this public product mapWithheld
Distribution packageNo installer, signed build, notarized package, or public release has been authorizedWithheld
Claim boundary
What remains unearned.
Not an installer, signed build, notarized package, or public release
Not proof of customer usefulness, adoption, or economic value
No automatic multi-model routing or silent cloud fallback
No external telemetry or account integration is claimed
The schematic is a sanitized derivative, not an application screenshot
Next evidence
Complete observed human-use work and the remaining distribution, accessibility, security, and supported-environment gates before any separately approved release decision.
