Views

Open the live surfaces by question, not by file tree.

Views should behave like an atlas. Filter the layer family first, keep the claim boundary explicit, then open the dashboard that matches the question you are actually asking.

Live explorer

Filter the stack before you open a dashboard.

Nightly interpretation, portable event stress, supportive non-stress layers, and output surfaces all live in the same repo. This explorer keeps those lanes separate so the route you open still means what you think it means.

Explorer

Choose the layer family first.

Use the filters below when you want the explorer to narrow to a specific claim family: stress interpretation, non-stress support, or portable transport. Leave it on all when you are orienting the full stack.

5 live dashboards 2 portable surfaces 2 output surfaces

Surface index

Each live layer should be reachable in one move.

Night Layer 12 visible units
4 accepted 7 experimental 1 support
Open layer
Event Layer 6 visible units
3 accepted 2 experimental 1 support
Open layer
Daily Challenge Layer 8 visible units
2 accepted 4 experimental 2 support
Open layer
Non-Stress Daily Layer 11 visible units
6 accepted 4 experimental 1 support
Open layer
Non-Stress Portable Families 3 visible units
0 accepted 1 experimental 2 support
Open layer

Guardrails

Keep the lane explicit before you open a dashboard.

  • Stress interpretation surfacesNight Layer and Daily Challenge stay inside governed interpretation and cohort-specific signal, even when they support participant or professional rendering later.
  • Portable transport surfacesEvent Layer and Non-Stress Portable Families matter when the question is transport. They should not be read as next-day sleep interpretation layers.
  • Supportive non-stress surfacesNon-Stress Daily keeps anxiety, mood, fatigue, and somatic context visible without claiming strong portability across cohorts.
  • Output surfacesParticipant and institutional pages are reporting layers built on top of approved routes, not separate model families.

Live dashboards

Open the deeper analytical surface once the lane is clear.

These cards preserve each layer’s own status, best visible signal, and direct route to the underlying dashboard without collapsing the stack into a single generic view.

night

Night Layer

4 accepted 7 experimental accepted

Nightly routes are the core operational layer. They carry held-out signal, interval calibration, governance, and deployment status.

Best visible signal Novartis D0 fatigue contextual interpretation
heldout_r20.4350
heldout_mae1.7972
heldout_rmse2.2791
coverage_pct80.2118
interval_width5.1123
transport_r2-0.1106
Open layer dashboard

event

Event Layer

3 accepted 2 experimental accepted

Event models remain separate from nightly interpretation. They are portable for acute physiological stress, not for next-day sleep claims.

Best visible signal Portable family stress event
mae0.6775
rmse0.8182
r20.3164
Open layer dashboard

daily

Daily Challenge Layer

2 accepted 4 experimental accepted_challenge

Daily challenge cohorts show where temporal memory helps within cohort, even when transport still fails across cohorts.

Best visible signal Boston anxiety D0 temporal
mae1.3178
rmse1.6673
r20.1685
rows20112
participants925
feature_count91
best_modelextra_trees
Open layer dashboard

nonstress_daily

Non-Stress Daily Layer

6 accepted 4 experimental accepted_challenge

This layer keeps anxiety, depression, and somatic support visible without overstating clinical portability.

Best visible signal Novartis depression D0 temporal
mae1.2722
rmse1.6985
r20.3454
rows4818
participants196
feature_count292
best_modelhist_gbm
Open layer dashboard

nonstress_family

Non-Stress Portable Families

0 accepted 1 experimental experimental

Portable non-stress families remain research references. Anxiety is closest to usable; depression and somatic burden are still below transport readiness.

Best visible signal Anxiety
portable_mean_r20.0202
route_replay_r2-0.0466
coverage_pct79.8680
rows303
participants103
feature_count10
Open layer dashboard

Adjacent surfaces

Keep the reporting and governance surfaces close to the explorer.

Views is the live dashboard atlas. These companion surfaces keep the broader project legible: public guardrails, participant-facing outputs, and institutional material for collaboration or pilots.

Guardrails before interpretation

  • Project overviewOpen the overview surface to re-anchor what Butterfly Effect is and is not trying to do.
  • Validation boundaryOpen validation when you need to check held-out performance, transport limits, and route approval status.
  • Evidence layerOpen evidence when you need the literature or intervention side, not just model output.
  • Participant logicOpen participant to see how approved nightly routes turn into governed participant-facing return.

Participant-facing access

This is not a separate consumer product. It is a longitudinal reporting layer built on top of approved routes and the same governed interpretation logic used elsewhere in the stack.

Institutional materials

These surfaces package the same system for pilots, collaborators, and data partners without pretending the public landing is already a clinical product.