A stack session is a coherent block of time where behavior, dosing, and outcomes are interpreted together.
Why it matters
Session boundaries keep a one-off context from being over-generalized.
Session definitions
- day session: one waking cycle and dose map
- training session: pre/post performance windows
- weekly session: aggregated pattern view
Interpreting adherence by session
- one late dose in a low-intensity day may be noise
- repeated drift in high-demand sessions signals protocol mismatch
Recommended journaling density
- low-complexity sessions: 1–2 outcome markers
- moderate sessions: timing + symptom + context
- high-risk sessions: full manual detail and route context
Practical action step
Define session boundaries before a new cycle to keep review and guardrails interpretable.
Uncertainty and limits
- Evidence is limited on the best session bucket size for every use case.
- Evidence is limited on whether all outcome shifts are stable across schedule changes.
Cross-site references
How this appears in Unfair
Session aggregation shapes trend charts and determines when scoring emphasizes consistency versus flexibility.
Clinical safety note
If session-level variance jumps after a change, reduce complexity and review for adverse-sensitivity patterns.