We'll tell you the principles. We won't tell you the recipes.

This page is for the visitor who wants to know whether the system is honest about what it does and doesn't know. Principles and constraints are public; the implementation recipes that compose them are the moat. The coach's language is bound by what the system is allowed to claim about you, and that boundary is what we can describe in detail without giving away how it's enforced.

The evidence ladder

The coach can't say something works for you until the evidence supports the claim strength. Five rungs, plain language.

01
Tested (causal). Repeated, validated, will hold unless the data changes. The coach can recommend.
02
Repeated pattern (observational). Seen multiple times in your data, not yet under test conditions. The coach surfaces it as a likely-true.
03
Worth testing (tentative). A signal the system noticed, flagged for a real test. The coach proposes the protocol.
04
No detectable effect. We tested it. The signal isn't there at the strength we'd act on. The coach says so.
05
Too noisy to call. Real life confounded the read. The coach names the confounders and the next useful measurement.

When the data isn't enough

Two artifacts. The first is a protocol that didn't move what it was supposed to. The second is a window where life got in the way of the read.

No useful signal on the named outcome14 nights / 2026-03-29 → 2026-04-12

Magnesium did nothing for my sleep score. I kept taking it.

Window: 14 nights at 420 mg bedtime
WHOOP sleep score: ±2 points (null)
Subjective sleep: no step-change
Best night H10 RMSSD: 33.3 ms (+8.7 vs prior)
Peak-hour H10 RMSSD: 41.7 ms (program high)
Diastolic BP floor: 86-88 mmHg (3 sub-90 readings)

The hypothesis on the named outcome (sleep) is not supported. A different mechanistic arm, autonomic and vascular, is moving. Recommendation: keep the protocol, change what we measure to verify it.

Keep, reassign outcomeTier: Tentative

Too noisy to callDays 26-29 / 2026-04-05 → 2026-04-08

We tried to read this window. Real life confounded it.

Window: 4 nights (Apr 5-8)
Sleep duration: ~3.0 / 5.25 / 4.5 / fragmented hours
H10 RMSSD: not captured / 26.3 / 22.4 / fragmented ms
Mean sleep HR: not captured / 65.5 / 66.3 / 70+ bpm

Confounders named

Personal stress, 2-hr wake periods
Easter family disruption
Children waking, dogs added Day 27
<1200 cal / day x3 (appetite suppression)
Magnesium form change (pressed → capsule, ruled out)
Skin temp +2.7 °F deviation, sympathetic thermoregulation

The system named what got in the way of the read and what would close it. That's a verdict.

Next useful step. Four consecutive low-stress nights with matched sleep duration and full stack compliance, the cleanest comparison the data hasn't seen yet.

InconclusiveTier: Too noisy

How we know the methods are real

We run our own research program on the math behind the coach. Methods get validated against real data before they're allowed to make a claim about you.

The principles we'll talk about: an evidence ladder that bounds what the system can say, individual-level error control so small samples don't produce false discoveries, and honest uncertainty intervals when the system makes a claim. Principles and constraints are public. The implementation recipes that compose them are the moat.

Why I built this

I've worn a Whoop for six years and a Garmin for thirteen. I've logged thousands of weights. I have lab panels going back further than that. The first time I asked a general-purpose LLM to read all of it together, it gave me an answer that sounded right and forgot the next morning.

I built DN1 because I wanted a system that remembered. I wanted something that, when I told it I'd tried magnesium for three weeks and my sleep score hadn't moved, didn't double down or capitulate. I wanted it to look at the autonomic and vascular markers the sleep score wasn't capturing and tell me whether something else was going on.

The first user is me. The methods exist because I had to know whether what I was doing was working. The career-arc framing is the easy version of the story. The hard one is: I have years of data and I didn't trust any tool I could find to read it the way I'd read it.

Test-change-verify on a cheap marker41 days / 2026-03-10 → 2026-04-20

BP dropped 25 systolic and 16 diastolic in 41 days. No new prescriptions. One $20 cuff and a list of mechanistic levers.

Day 0: 146 / 102
Day 17: 128 / 92 (first sub-130 systolic)
Day 28: 120 / 88 (program low both arms)
Day 41: 121 / 86 (diastolic floor confirmed)
Day 43: 122 / 87 (third consecutive sub-90 diastolic)
Window total: -25 systolic / -16 diastolic in 41 days
Strongest single lever: weight loss (-9.4 lbs)

Multi-input mechanism stack pulled in parallel: weight loss, magnesium 420 mg bedtime, nattokinase 12,000 FU, omega-3, taurine 3 g, isometrics. Daily morning rested-protocol BP measurement at home. No clean lever-isolation by design. Multi-attribution is the point. The principle is test-change-verify on a cheap marker. Escalate only if the levers fail.

Stack heldTier: Tested

Get on the list

If you've read this far, you're the user. Join the waitlist.

Join the waitlist