What it watches
Longitudinal sleep timing, continuity, nocturnal cardiovascular load, movement, and repeated self-report signals.
Sleep Interpretation Research
Reading how subtle changes at night may precede changes the next day.
The flap of a butterfly’s wings can be felt on the other side of the world.
Butterfly Effect explores how small changes in sleep and overnight physiology may precede later changes in stress, symptoms, and daily burden. The public surface is designed to explain that idea clearly without blurring the very different layers of evidence underneath it.
From Signal To Surface
The project is easier to understand when it is read as a flow, not as a stack of technical labels.
These three blocks are the simplest entry into the system: what is observed, what is built from it, and what the public surface actually gives back.
What it builds
Nightly interpretation routes, event stress models, daily challenge layers, and portable research families with explicit governance.
What it returns
A readable interpretation surface for institutions, participants, and professionals: signal, limits, validation posture, and evidence links kept visible at the same time.
Visible cards
40 night, event, daily, and family surfaces exposed without flattening them into one false product claimAccepted units
15 cards or families with signals the current evidence can defend inside their intended scopeExperimental units
18 research layers that remain useful but still fall below deployment or transport thresholdsMain bottleneck
Night transport cross-cohort nightly portability still limits the strongest public claim the project can makeAudience Entry
The same project has three different public reading paths.
This switcher keeps the entry point readable. It lets a new visitor move straight into the right surface instead of reading the entire stack in the wrong order.
Start here if you want the method
What this path gives you
- Research postureStrongest in `stress`, explicit limits elsewhere.
- Live layersOpen the governed dashboards and route cards
- ToneMethod first, no flattened “one model” story.
Start here if you want a collaboration path
- One-pagerOpen the institutional entry point
- Data requirementsOpen the technical data pack
- Pilot protocolOpen the default first-pilot frame
What this path gives you
- Serious askOne cohort, one endpoint family, pre-screen before transfer.
- GovernanceOpen the intake and linkage gate
- TargetingSee the current shortlist and raw-night benchmark
Start here if you want the human-facing layer
- Participant ReturnOpen the governed weekly return surface
- DirectoryOpen the live participant-facing outputs
- Primary sampleOpen the first weekly report
What this path gives you
- No sleep-app framingWeekly longitudinal interpretation, not single-night scoring.
- Professional companionSame payload, stricter technical view, clean handoff formats.
- Governed scopeOnly audited nightly stress routes can enter this layer.
Research posture
One project, five visible layers, five different evidentiary roles.
Once the core idea is clear, the rest of the site stays readable by showing where each layer is strong, where it is limited, and what kind of claim it can legitimately carry today.
Night Layer
Within-cohort interpretation
High · Held-out R² 0.4350
Limited
Operational
Blocked by nightly transport
Event Layer
Acute stress portability
High · R² 0.3164
Portable
Separate stack
Must stay separate from night claims
Daily Challenge Layer
Temporal challenge layer
Moderate · R² 0.1685
Challenge only
Challenge
Good within cohort, weak across cohorts
Non-Stress Daily Layer
Supportive daily reading
High · R² 0.3454
Challenge only
Mixed support
Support visible, portability limited
Non-Stress Portable Families
Portable research family
Low · Portable mean R² 0.0202
Emerging
Research only
Below transport readiness
Pages
The home stays light. The detail lives on dedicated pages.
The front page should orient, not flood. System structure, validation, evidence, and live analytical views now sit on their own pages so the entry point stays readable.
System
System
How the project is structured across night, event, daily, and portable-family layers, and why those boundaries matter.
Open pageBuilt
Built
What is already implemented: nightly routes, event stress, daily challenge layers, governance, evidence, and support.
Open pageValidation
Validation
What the current evidence can support, what it cannot, and where transport still fails across cohorts.
Open pageEvidence
Evidence
The open cohorts, support cohorts, and evidence-linked reporting stack underneath the public surface.
Open pageParticipant
Participant Return
A participant-facing research-return layer and a professional companion built on approved nightly stress routes, not on a separate consumer stack.
Open pageViews
Views
Direct access to the live dashboards and layer-specific surfaces already materialized in the repo.
Open page