# Weekly log

One entry per week. The hypothesis and the metric are written **before** the change ships;
the measurement is filled in by the following week's run. A week without a measurement is
an unfinished week.

| Week | Date | Change | Hypothesis | Metric watched | Expected | Measured | Verdict |
|---|---|---|---|---|---|---|---|
| 0 | 2026-10-24 | Instrumentation: Plausible tag on 1,206 pages, `Affiliate Click` / `Outbound Click` custom events, UTM on 479 outbound links, CTA blocks on 6 homepages + 6 hosting hubs, weekly loop installed | Without measurement every change is a guess | all | baseline established | n/a (setup) | keep |
| 1 | 2026-10-24 | `.agents/product-marketing.md` (d82af02): ICP, pains, objections, proof policy, positioning — the source of truth every later week reads | Copy decisions were being re-litigated weekly; without fixed positioning each change invents its own | none (enabler); guardrail = no ranking loss | no regression | pending (week 2 run) | keep |

---

## Entry template

```markdown
### Week N — YYYY-MM-DD

**Shipped:** <what changed, with commit hash>
**Hypothesis:** <why this should move a number>
**Metric:** <the one number that decides>
**Expected:** <direction and rough size>

**Measured (week N+1):** <actual, from growth_week.py>
**Verdict:** keep / revert / adjust — and why

**Next:** <carried into the following week>
```