# Trial health baseline

A reusable skill the "Catch a stalling POC before it goes dark" recipe pulls in. Add it once and every agent on the team can use it.

Define what healthy usage looks like at each trial stage so a stall reads against a real bar.

## Method
1. Define baselines separately for kickoff, mid-POC, and final-week stages.
2. Pull the metrics from PostHog: login frequency, key feature adoption, active user count.
3. Set a minimum expected value for each metric at each stage.
4. Refine the baseline as more trials close won or lost — widen or tighten thresholds based on outcomes.
5. Store the current baseline in memory so every daily run compares against the same bar.

## Rules
- Healthy-usage thresholds per trial stage: (set on first run, then stored in memory).
- Which PostHog events count as meaningful activity: (set on first run, then stored in memory).
- Update the baseline only after a trial's outcome is known, never mid-trial.
- Keep separate baselines per stage — a mid-POC trial is not judged against kickoff activity.

## Output
A stored baseline in memory: minimum usage values per metric, per trial stage, with the last-updated date.