BASEPERSONAL EVIDENCEExplore BASE
BASELINE-ANCHORED SENSING & EVALUATION

Change is personal.
So is the evidence.

Understand what changed for you.
How much. How confidently. In what context.

Turn longitudinal wearable data into an inspectable record of personal change, anchored to where you started.

Working research preview · Synthetic demo · Local CSV analysis
ONE PERSON. TWO WINDOWS.ILLUSTRATIVE
Your reference
stays in view.
BASELINEFOLLOW-UPEVENT
≡
Evidence, attached.Reference · uncertainty · context
A MORE USEFUL UNIT OF ANALYSIS

You, over time.

Population knowledge provides context. Your own history provides a personal reference. BASE makes that comparison visible and reviewable.
01 / ANCHOR

Keep the starting
point in sight.

A fixed baseline preserves the original comparison. A rolling view shows how your pattern evolves. Explore both without quietly moving the goalposts.

Explore the two views
02 / INTERROGATE

Ask what else
could explain it.

Travel. Illness. Missing data. Inspect the context and compare results with flagged days excluded. The uncertainty belongs beside the estimate.

Test a confounded scenario
03 / EVIDENCE

Take the reasoning
with the result.

Export the windows, methods, coverage, assumptions, and data fingerprint behind your analysis. Every result should be possible to inspect.

Create an evidence receipt
THE FIRST QUESTION IS YOURS

Did the change
change anything?

Explore a sleep schedule, inspect a travel confound, or bring a daily CSV from one individual. Start with a question you can actually measure.

Open the working preview 3 scenarios · 3 outcomes · Transparent methods

Built for exploration and pilot design. Clinical validation, direct wearable connections, and team workflows are future development.

Bring your own baseline.

Import daily observations for one person. Your file stays in memory on this device and clears on refresh.

Up to 2 MB · 2,000 rows · One observation per day

Required: date (YYYY-MM-DD), and at least one of sleep_hours, resting_hr, hrv_ms. Optional: valid (true/false), context (any nonempty value flags that day). Missing metric values are left out, never imputed.

Use one consistent device and metric definition per file. Data bounds catch malformed values; they are not clinical safety thresholds.

Your evidence, attached.

Unsigned snapshot. No raw observations are included. Retain your source file to reproduce the analysis.