Live
Public website source
The public /status, /join, and /journey routes are live. /join uses bounded wording, and /journey presents the available first-slice prototype.
meUus has begun as a documented vision, a public website codebase, and a bounded Journey Mode prototype. This page separates what exists now from what is prototype, in development, planned, or not yet available.
These labels are evidence boundaries for public copy. They are not a claim that every service is operating.
Live
The public /status, /join, and /journey routes are live. /join uses bounded wording, and /journey presents the available first-slice prototype.
Browser-local prototype
Journey Mode is available as a local-first, non-diagnostic first-slice prototype. It includes Knowledge Before Action, one quest, optional written reflection, and an internal checkpoint. Explicit preference confirmation and the local browser clear/restart control are completed and live verified. Journey data remains in the current browser.
Live bounded pilot
The public meuus.app production pilot has verified sign-in, Dashboard, Profile, authenticated records, Growth Paths, full-reload session restoration, and sign-out. This does not activate public AI analysis, DLAS runtime, payments, rewards, subscriptions, or automated decisions.
Planned
The Development Lens and Assessment System is a future assessment and guidance concept. This repository does not yet contain a DLAS engine, schema, scoring model, validation method, consent model, or Journey integration contract.
In development
The website describes nine intended pillars as an ecosystem direction and content model. The repository does not prove operating services, partners, pilots, professionals, customers, revenue, or public impact.
Not live
Public AI analysis, DLAS runtime or scoring, payments, rewards, subscriptions, automated decisions, and the full operating ecosystem are not verified or live.
Day One
Day One should be understood as truthful continuation: a public informational website, a clearly labeled Journey prototype, a reliable contact path, and careful evidence-building. It is not a complete ecosystem launch.
Where this fits · Verify
Current verified boundary
The app evidence is limited to its accepted production flow and authenticated records. Broader systems remain future work. Public claims must stay specific and tied to implementation, validation, review, and operational ownership.