endurance-coach-n1-validation-campaignlisted
Install: claude install-skill maxeskell/personal-training-app
# n=1 validation campaign — is this signal real for THIS athlete?
**Use this when** you are about to trust, ship, or change a finding from the insight engine (`src/insights/`)
and you need a repeatable go/no-go procedure that ends in "confirmed" or "exploratory" — never a hunch. The
core files are `monitoring.ts`, `correlations.ts`, `efficiency.ts`, and their shared primitives in `stats.ts`.
**Don't use this when** you want:
- the *derivations* of the estimators (why effective-N, why Fisher-z, why Bonferroni-before-BH, how the
permutation null works) → **`endurance-coach-proof-and-analysis-toolkit`**.
- the general *epistemics* (evidence bar, pre-registration template, idea lifecycle) → **`endurance-coach-research-methodology`**.
- the *meaning* of a metric (what CTL/HRV/EF/decoupling is) → **`endurance-domain-reference`**.
- the *test conventions and CI contract* → **`endurance-coach-validation-and-qa`**.
- to *ship* the change → the gate lives in **`endurance-coach-change-control`** (this campaign routes through it at Phase 5).
**Vocabulary (defined once).** *n=1* = a single athlete's own data, so group statistics don't apply and everything is
autocorrelated. *Autocorrelation* = today looks like yesterday (fitness, HRV, weight all drift), which fakes strong
correlations. *effective N (effN)* = the sample size after discounting for that drift — the honest count. *CI* =
confidence interval; "CI excludes 0" = the effect is distinguishable from nothing. *FDR* = false-disco