For participants
Readable weekly interpretation with explicit confidence, limits, and review nights.
weekly
baseline-relative
non-diagnostic
Participant-Facing Layer
Research return for people and professionals.
This layer exists to return weekly longitudinal interpretation from the same governed engine used elsewhere in Butterfly Effect. It is deliberately narrower than the institutional stack, and deliberately more serious than a consumer sleep product.
Reading Frame
The layer stays useful only if it stays narrow.
This is not a sleep score, not a single-night explanation layer, and not a diagnostic surface. The point is to summarize repeated night patterns, baseline-relative shifts, and observed links with next-day burden in a reviewed weekly form.
For professionals
The same weekly payload, but in a stricter operational summary for review and handoff.
same engine
companion summary
PDF-ready
For the project
A human-facing layer that does not weaken the research contract or invent a second inference stack.
route audit
audience contract
stress-only for now
Audience Switcher
One core, three different contracts.
The same weekly interpretation can be read three ways. The content changes with the audience, but the route governance and report provenance stay attached throughout.
Participant contract
- What it returnsWeek-at-a-glance, dominant domains, shifts vs baseline, observed links, review nights, and limits.
- What it does not doNo diagnosis, no disease-risk statement, and no single-night certainty language.
- Current focusStress / next-day burden only.
Professional contract
- Same payloadThe companion summary is generated from the exact same weekly report payload.
- Use caseStructured review, supervision, or participant handoff with clearer operational readout.
- FormatsHTML, print-ready HTML, JSON, and PDF.
Governance contract
- Route entryOnly explicitly approved routes that also pass route-card audit can enter.
- Attached safeguardsAudience contract, route audit, and governance snapshot remain inside the output payload.
- Why this mattersThe human-facing layer stays serious because it inherits the same methodological discipline as the rest of the system.
Live Reviewed Samples
Two cohorts, one reviewed weekly return surface.
These are not mockups. They are real outputs from the approved nightly stress routes that currently define the participant-facing layer.
LifeSnaps · `stress_d1_contextual`
Primary sample route for next-day burden. This is currently the clearest participant-facing example of the weekly return format.
D+1 stress
approved route
participant + professional
PMData · `stress_d0_contextual`
Secondary approved route so the layer is not tied to one cohort or one latency frame.
D0 stress
approved route
participant + professional
Materials And Build Path
The layer is specified, audited, and reproducible.
This page is not just a sample gallery. It also exposes the documents and commands that keep the layer defendable.
Specification and contracts
- Layer blueprintOpen specification
- Eligibility auditOpen route-card audit
- Audience contractsOpen participant and professional contracts
Build commands
- List approved routes
./.venv/bin/python -m neural_echo_system.build_participant_weekly_report --list-routes - List contracts
./.venv/bin/python -m neural_echo_system.build_participant_weekly_report --list-contracts - Refresh audit
./.venv/bin/python -m neural_echo_system.audit_participant_facing_routes --output-dir reports/participant_facing
Public context
- Public participant pageOpen the narrative-facing public surface
- Validation frameOpen the validation boundary
- Live viewsOpen the layer index