Participant Return

A participant-facing research-return layer, not a consumer sleep app.

This surface exists to return weekly longitudinal insight to people and a companion summary to professionals, while staying tied to approved nightly routes, explicit limits, and the same report provenance used elsewhere in the system.

Frame

The participant layer stays useful only if it stays governed.

The point is not to explain one isolated night. The point is to summarize repeated patterns, baseline-relative shifts, and observed links with next-day burden in a form that is readable without dropping the methodological safeguards.

Participant weekly report

  • CadenceWeekly, longitudinal, and baseline-aware rather than reactive to a single night.
  • ContentShift vs baseline, dominant night domains, observed links with burden, nights worth reviewing, and explicit confidence limits.
  • Claim boundaryNo diagnosis, no disease claim, and no medical advice disguised as interpretation.

Professional companion

  • Same payloadThe companion is generated from the exact same weekly report payload, not from a second inference stack.
  • Use casePsychologists, clinicians, and research staff can review the same week with more technical structure and clearer caveats.
  • HandoffBoth surfaces are materialized in HTML, JSON, print-ready HTML, and PDF.

Current access

The layer is already live and reviewable.

These are real outputs built from approved nightly stress routes. They are shown here as reviewed examples of the return surface, not as a separate wellness product.

Governed scope

Participant return, professional review, and institutional research are different procedures.

The same core system can serve all three, but the contract changes with the audience. Participant return is narrow and weekly; professional review is companion-oriented; institutional work still goes through intake, governance, pilot, and cohort-level validation.

Participant contract

  • UnitWeekly longitudinal window, not an isolated night.
  • Current routes`lifesnaps_stress_d1_contextual` and `pmdata_stress_d0_contextual` only.
  • BoundaryResearch return, not diagnosis and not consumer scoring.