LifeSync / inside the system Try the demo

A personal system. A considered architecture.

A day is more
than a score.

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

LOCAL FIRST ↗
LifeSyncOn this device
GOOD MORNINGMake room
for your day.
READINESS82/100
SLEEP7h 48m
TODAY'S RHYTHM
✓ Morning daylight 08:10
✓ Gratitude 08:25
MEDITATION · RUNNING04:32
No connection needed.
TodaySessionsInsightsBody
THE SIGNAL, NOT THE NOISEPatterns with their
sources attached.
Illustration · sample values
01 Keep daily use local.02 Make evidence traceable.03 Share by choice.

01 / One place, four perspectives

Less switching.
More continuity.

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.

01

A record of the day,
not another inbox.

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.

  • Daily habits and supplements
  • Quick access to Focus & Pomodoro
  • Automatic morning, daytime and evening artwork
  • Editable catalogue, without throwing away records

02 / Follow the data

The phone is a home.
Not a remote control.

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.

Where each part lives

Current private-product architecture
Architecture showing Android local storage and outbox, web and Mac clients, a self-hosted HTTPS proxy and app container, persistent storage, and deliberately selected external integrations.
ON THE PHONE

Useful before it syncs.

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.

ON YOUR SERVER

One reconciled record.

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.

ON THE MAC

A deliberately small companion.

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

Connection lost.
Work kept.

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.

01 / local commit

The practice is saved now.

The phone writes the session to SQLite immediately. Daily use does not wait for a reachable server.

EXAMPLE SESSION · FICTIONALMeditation 05:00
Saved on this phoneNetwork unavailable

Interactive explanation, not a live connection test.

A retry must not become a duplicate.

Record synchronization
Sequence diagram: a phone saves locally, pulls changes and pushes a stable operation ID after reconnection; the server applies it once and other clients see the accepted revision.

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

Every number
has a way in.

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.

OURA · IMPORTED

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.

82 readiness /100
Fictional example. Public connection is simulated.
MUSE · REVIEWED EXTRACTION

A screenshot is evidence.
Not a raw data stream.

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.
HABITS · DERIVED

Use the log
you already keep.

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.

4 / 5 practices
Illustrative progress. Unknown is not automatically missed.

Models & agents

Interpretation by permission.

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

Show the product.
Not a person's life.

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.

The public/private boundary

No shared database or credentials
Two separate boundaries: a public static showcase and visitor-local synthetic database with outbound API traffic blocked, and an authenticated private application with personal storage and optional external requests.
01 / TRANSPORT

HTTPS protects the journey.

Authenticated encrypted transport protects traffic. The server can still read ordinary numerical records for charts and analysis.

02 / PRIVATE CONTENT

Encryption is selective.

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.

03 / MEDIA CHOICE

Local means this device.

Local files are not silently uploaded or magically present on another device. Programmes and records synchronize; media availability follows the storage choice.

04 / PUBLIC PREVIEW

Nothing personal underneath.

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

Ambitious.
Specific about the present.

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 status · documented 21/10/2026
CapabilityPersonal productPublic showcase
Today, habits, trends & bodyShared working interface and record modelInteractive, synthetic data
Sessions, sound & programmesLocal player, editable programmes and saved historySame controls; advanced visual builder omitted
Phone, web & Mac timingImplemented synchronization; device acceptance remains separateSingle-browser timer; pairing is simulated
OuraImplemented server connectorInvented sleep, readiness and activity
Muse screenshots & model analysisBeta, deliberate send and mandatory reviewExample reviewed metrics; no paid calls
Read-only agent accessSelected, expiring and revocable scopesSimulated grant controls, no usable token
WHOOPPlanned connectorClearly labelled conceptual flow
Full health-data end-to-end encryptionInvestigated, not implementedNo private health data to encrypt
Reminders & floating controlsOpt-in; operating-system permissions and device checks requiredNo 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

One day. Four perspectives.
A little more context.

Open the interactive demo ↗