Stack activation is when a planned stack moves from saved intent to active execution.
Why it matters
Clear activation reduces accidental drift between what you built and what you actually run.
One-time activation and states
A stack has:
- drafted
- active
- paused
- deactivated
Use pause intentionally when adverse signs rise.
24–72 hour safety checks
- check adherence within first completion window
- confirm no new adverse flags
- validate route and timing consistency
Reactivation process
When reactivating, re-run baseline checks and confirm stack context has not materially changed.
Example: adverse-event driven deactivation
- adverse report arrives 12 hours after start
- stop active stack
- review top-risk ingredients and interactions
- restart only with narrowed scope and updated intent
Practical action step
Use a short activation checklist before every start, including route, time windows, and escalation thresholds.
Uncertainty and limits
- Evidence is limited on exact timing for all stack types to detect harm.
- Evidence is limited on behavior drift after repeated pause/reactivate cycles.
Cross-site references
How this appears in Unfair
Activation state affects reminder logic, recommendation visibility, and safety checks during cycle transitions.
Clinical safety note
If adverse events continue after reactivation, require clinician guidance before any additional stack starts.