Install the phone app, set up the local Gemma model from CAST's Model setup, and keep the Personal Data Net inspectable, exportable, pausable, and deletable before any wider public release.
The private beta starts with the standalone CAST phone strategist, then keeps PC, Chromebook, and watch setup paths separate as the suite grows.
Later beta lane: Stella runs on the computer, CAST runs on the phone, and the Personal Data Net lives primarily on local hardware.
Later beta lane: a Chromebook Linux environment can host the local command center while CAST remains the mobile problem-solving front end.
The current lane is phone-first. It installs the local phone model through Model setup, can recover from a Downloads copy, keeps approved notes, and works without a PC or watch.
Manifest-driven release cards. Every artifact requires explicit user approval and checksum verification before install.
This is the core marketing promise and the engineering constraint. Private beta should prove the promise before public rollout.
Personal memory, raw private chats, local databases, model paths, tokens, and API keys stay on the user's device unless explicitly exported.
Bug reports, release checksums, hardware summaries, and lessons can go to the beta hub after redaction and user approval.
Camera, mic, location, watch, and file access should be requested only when the user taps that tool and understands what will be stored.
Stella and the phone sidekick can talk inside a user-started room. When the room ends, model-to-model chat stops.