Chat is live-shaped
The Chat surface sends the same request family used by the Apple app.
Browser portal
Enter Lumela
This is the browser doorway into the same Core Four service used by the native apps.
Checking staging service...
Lumela account access is not open from the web yet.
Staging portal
Today
Checking staging service...
Ready path
One shell. Every device.
The browser portal is now staged to carry Account, Chat, Spaces, Build, Signals, and service status across desktop, phone, and tablet views.
Account is the boundary
The shell keeps account context visible before the rest of the portal grows.
Responsive by default
The same portal bends across browser phone, tablet, and desktop shapes.
Ask the Core Four from the browser portal.
Shared context
Spaces
Spaces are where communities, rooms, members, shared knowledge, announcements, and shared context will live.
Rooms
Human conversation surfaces will appear here only after the shared Room service path is ready.
Knowledge
Shared references and community material will stay account-bound before any public visibility is offered.
Members
People and roles belong inside the active Account and Space boundary.
Announcements
Public memory and community sharing will require explicit user action before publishing.
Work that can be held
Build
Build is where projects, artifacts, drafts, active work, and created outputs will live without moving the Core Four runtime into the browser.
Projects
Project state will stay tied to the active Account, Space, or Conversation.
Artifacts
Saved outputs will become recoverable from the context that owns them.
Draft Room
Bring in a Human and Draft Room behavior will use the conversation promotion contract when service support is ready.
Usage
Model work will remain tied to the signed-in account usage wallet.
What asks for attention
Signals
Signals are where Rillo, VIBE, GUIDE, Circles, Alarms, Routines, Events, notifications, and signal rules will live.
Ownership boundary
Account
Account is where profile, plan, usage, payment reloads, devices, privacy, Private Vault entry, and sign out belong.
Remaining usage
$1.00
Usage will update from the Core Four service when a signed-in account session is present.
Private Vault
Secrets open through an encrypted storage path and should require fresh device approval before values are revealed.
Devices
Trusted browser/device entries will appear here after browser passkey completion is implemented.
Privacy
Memory, sharing, export, and deletion controls belong inside this account boundary.