Nightly signals,
without retyping.
Sleep, readiness, heart rate variability and supported timing readings arrive through the personal connector. Trend selectors preserve the available metrics, dates and units.
A personal system. A considered architecture.
Sleep, habits, focused work and practice belong in the same picture. A phone-first control centre that works without a connection, then brings your devices back into step.
Interactive demo · invented records · no account or real device connection
01 / One place, four perspectives
The showcase uses the product's actual screen and domain code, not a simplified set of screenshots. Its data layer is replaced at build time with invented, browser-local records.
Fast daily logging with amounts, times and private notes. Visible habits are evaluated from the entries you already make, completed sessions and supported Oura readings, rather than asking you to log everything twice.
Changing a display label or hiding an item preserves its stable identity and recorded history.
Countdown or count up, editable presets, separate interval and ending bells, layered sound, voice and gradual binaural stages. Review the completed record before choosing whether to save it.
The personal edition also supports ordered or shuffled image/video playlists and word overlays. That advanced visual builder is intentionally not shown in this public demo.
Switch between readiness, sleep, heart rate variability and other available metrics. Track chosen habits, daily counts and weekly practice or focus time alongside the underlying source coverage.
Missing evidence stays unknown. Associations compare observed groups; they do not establish that a habit caused an outcome.
Record measurements consistently and follow them over time. The same record model supports the phone's local database and the authenticated web interface.
A measurement keeps its date and unit. Charts do not turn ordinary tracking into a clinical assessment.
02 / Follow the data
Daily actions commit on the phone. A self-hosted service reconciles records when a connection returns; the browser uses authenticated web access. The small Mac companion mirrors timing, not the full health database.
Shared interface in a Capacitor Android app. SQLite stores records, accepted recovery copies and a durable outbox. Media stays in application storage unless cloud storage is chosen.
A Node.js service and SQLite database sit behind an authenticated HTTPS boundary. Oura import, read-only agent access and explicitly requested model calls run here.
A native floating Focus window shares live timing and acknowledges controls. Pairing uses a private local file, not Mac Keychain. It does not receive the private media library.
03 / An offline action, end to end
Synchronization is an explicit protocol, not a timer that overwrites whichever copy is older. Follow a simple example: logging a five-minute practice while offline.
The phone writes the session to SQLite immediately. Daily use does not wait for a reachable server.
Interactive explanation, not a live connection test.
Delete without resurrection. Deletion markers remain in the change feed, so an offline copy does not silently recreate a removed record.
Recover without dropping pending work. Accepted copies and unsent operations are kept separately. A changed server epoch triggers recovery rather than trusting an obsolete cursor.
Mirror without double playback. A running session has one playback owner. A remote control is a request awaiting acknowledgement; disconnected devices cannot guarantee live agreement.
04 / Evidence before interpretation
One view should not imply one source or one level of certainty. Imported readings, reviewed screenshot values and derived habit results retain their different meanings.
Sleep, readiness, heart rate variability and supported timing readings arrive through the personal connector. Trend selectors preserve the available metrics, dates and units.
Multiple screenshots can support one session: duration, calm time, birds, recoveries, Cognitive Performance and Brain Recharge where visible. Values are reviewed before saving.
Brainwave powerbands and brain oxygenation graphs can be retained as evidence images. Their curves are not converted into falsely precise measurements. Muse points are not tracked.
No direct headband streaming is claimed.A habit rule combines the chosen item, schedule and evidence. For example, five completed practices of at least five minutes can satisfy a daily repeated-session goal.
Models & agents
OpenRouter and supported providers can analyse deliberately submitted screenshots or selected numerical summaries. Agents receive expiring, revocable read-only grants for selected metrics, visible habits and reviewed Muse fields, not private notes or media. All such connections are simulated in the public demo.
05 / Separation is the architecture
The public showcase is not a guest account on the private service. It is a separately built static application with its own synthetic catalogue, storage namespace and fail-closed data adapter.
Authenticated encrypted transport protects traffic. The server can still read ordinary numerical records for charts and analysis.
Protected notes and chosen cloud media use client-side encrypted envelopes. The private-content passphrase is separate from device pairing. This is not full end-to-end encryption of every record.
Local files are not silently uploaded or magically present on another device. Programmes and records synchronize; media availability follows the storage choice.
Only synthetic modules enter the public bundle. No private database, keys, personal files or internal server addresses are included. Visitor changes and uploads remain in that browser.
06 / Built, simulated, next
Feature implementation, automated verification and real-device acceptance are different claims. The walkthrough describes the architecture; it is not proof that an untested device or provider flow has passed.
| Capability | Personal product | Public showcase |
|---|---|---|
| Today, habits, trends & body | Shared working interface and record model | Interactive, synthetic data |
| Sessions, sound & programmes | Local player, editable programmes and saved history | Same controls; advanced visual builder omitted |
| Phone, web & Mac timing | Implemented synchronization; device acceptance remains separate | Single-browser timer; pairing is simulated |
| Oura | Implemented server connector | Invented sleep, readiness and activity |
| Muse screenshots & model analysis | Beta, deliberate send and mandatory review | Example reviewed metrics; no paid calls |
| Read-only agent access | Selected, expiring and revocable scopes | Simulated grant controls, no usable token |
| WHOOP | Planned connector | Clearly labelled conceptual flow |
| Full health-data end-to-end encryption | Investigated, not implemented | No private health data to encrypt |
| Reminders & floating controls | Opt-in; operating-system permissions and device checks required | No permission requests or real reminders |
Personal tracking and pattern exploration, not a medical device or diagnostic claim. Community presets and model output are not proof of efficacy.
Now try the system