FT—EXP—04 / Design brief
BAYSE
Private health tracking
A private space for organizing medications, supplements, hydration and personal health routines. Know your baseline. Follow the change.
- Reference
- FT—EXP—04
- Discipline
- Product, brand and safety system
- Format
- Private web app, installable
- Access
- Private. Nothing is served without sign-in
01 / The mark
A baseline, and one thing that happened on it.
The Baseline Mark is three strokes. A vertical stem is the origin: the day you started keeping a record. A horizontal line is the baseline running forward from it. One orange stroke crosses the line: a single recorded event. The line carries on past it, because the record does.
Shown with no context it should read as measurement, never as medicine. There is no cross, no capsule, no device and no letter in the mark, and the name says nothing about what a person keeps in it. That neutrality is part of the privacy design, not a style choice.
stem · baseline · event
same geometry, no orange
still three strokes
02 / Colour
Graphite, warm white, and five percent orange.
Orange has one meaning: this is recorded, current or selected. It marks an event on the timeline, the active control, the end of a trend line. Orange never means danger, abnormal or high. Safety has its own colours, and they never appear without a border and a plain word beside them.
03 / Type and motion
A lab instrument, not a wellness app.
Baseline
Archivo 600
Wordmark and display. Uppercase, tracked .14–.18em. Plain geometric capitals; nothing hidden in the letters.
08:40 · 118/76
Archivo 500, tabular
Every number, date and unit. Figures line up in columns so a change is visible before it is read.
Entered by you
IBM Plex Mono
Micro labels and provenance. Small, uppercase, quiet. They say where a value came from.
The pulse. One signature motion: an orange marker lands on the baseline and a single thin ring travels outward over 1.1 seconds, then the date settles beneath it. It plays when a record is saved. No confetti, no bounce, no streaks, no rewards. People who prefer reduced motion get none.
04 / The brief
Track accurately. Preserve provenance. Show uncertainty. Protect the record.
BAYSE is a record, an organizer and a reference shelf. It is deliberately not an adviser. The design problem is how to be useful with health information while never pretending to be a clinician.
The job
Keep one private, continuous record of what a person takes and what they observe, in their own words and their own units, so they can see their own pattern and hand an accurate list to the people who look after them.
What you get
- A timeline of everything recorded, and trends over time.
- A current list of what you take, with a periodic review.
- Product labels copied as printed, and a notice when the same nutrient appears in more than one product.
- Lab results kept in the unit and range the lab reported.
- Measurements and symptoms, with timing.
- Export of everything, any time.
The line it holds
BAYSE does not diagnose, choose a treatment, suggest starting or stopping anything, or work out an amount for anyone. It does not add up what you take and judge it. It never turns a missing entry into a fact, intake into a body measurement, or two things happening together into cause and effect.
05 / Evidence
If BAYSE cannot show its source, it says so instead.
Every piece of reference information passes through one gate before it can appear. The gate is ordinary deterministic code, not a language model. A statement is shown only when it carries an identifier, the exact wording the source supports, a working link to that source, the kind of source, the population it applies to, its date, its limitations, a version and a date by which it must be checked again.
Anything that fails is replaced on screen by two words: RESEARCH REQUIRED. Every statement that passes has a View evidence sheet showing all of the above. Wording that promises outcomes or tells a person what to do is rejected automatically, and the build fails if an unsupported statement slips in.
Badges are monochrome. A source type is a description, not a score. Today's summaries are source-checked with AI assistance and have not been independently reviewed by a named clinician; the product says this on every sheet rather than implying otherwise.
06 / Provenance and safety
Every value says where it came from.
Provenance labels
Each record carries a small label: entered by you, copied from a label, from a lab report. A lab value keeps the unit and reference range printed on the report. BAYSE does not convert lab values or supply a range of its own.
Nothing is overwritten
A correction is a new version linked to the one before it. The history stays traceable, and the person can see what changed and when.
Urgent symptoms
If a person records a symptom on a short fixed list of warning signs, one plain screen appears first: contact emergency services or your clinician. It names no cause and offers no assessment. Then the record is saved as entered.
Quiet by default
The browser title is only the name. Reminders read "Check-in available". A discreet mode hides item names until tapped and hides the screen after a minute of inactivity.
07 / Privacy
Said plainly, including the parts that are not flattering.
Before a person finishes setup they read one short notice with six headings: what is stored, why, who can see it, what BAYSE does not do, how to export, how to delete. Only one thing is switched on by agreeing: storing what they choose to enter. There is no advertising, no analytics, no research use, no import from other apps and no sharing feature. If any were ever added, each would have its own switch, off until turned on.
Who can see a record
Other members cannot. The administrator's screen lists members, not their records. BAYSE is not an end-to-end encrypted vault: the person who operates the service has administrative access to the cloud project where records are stored, and the notice says so.
Deny by default
Without a valid sign-in the server sends only the sign-in page. The app, its scripts and its data all return "unauthorized". Every save is checked on the server against the same rules the app uses, and a person can only ever read their own records.
Yours to take or remove
Export to open formats or a readable summary at any time; exports ask for a fresh sign-in and warn that a downloaded file is no longer protected. Deleting the account removes the records and the sign-in.
BAYSE makes no claim of compliance with any health-privacy law. Those questions are written down and marked for a lawyer, not answered by the software.
08 / Status
What is live, what is waiting, what is not built.
| Part | State | Note |
|---|---|---|
| Timeline, trends, current list, review | Live | Append-only records with provenance labels. |
| Evidence gate and View evidence | Live | All published statements pass the gate; a named clinical reviewer is still to be appointed. |
| Product labels and repeated nutrients | Live | Reference values transcribed for seven nutrients so far; the rest say so. |
| Lab results with reported units, urgent-symptom screen | Live | |
| Layered data notice | Live | Whether it is sufficient consent under a given law is a question for legal review. |
| Fluids, and blood pressure, heart rate, temperature | Waiting | Built and tested. The app keeps them hidden until the server is updated to accept them, so nothing can be saved unchecked. |
| Checking items against each other | Not built | Needs a licensed, authoritative data source. It will not be built from guesswork. |
| Sharing, device imports, push notifications | Not built | Each needs its own opt-in and its own privacy review first. |