t4-p3-01authored1–3h

Define success metrics before looking at results

Define 2-3 success metrics - response rate without a nudge, time-to-digest, a satisfaction proxy such as reaction rate - and commit them before analysing any usage data.

Committed first so git can prove it. Metrics chosen after seeing the data are chosen to flatter it, and this is one of the few places that failure can be mechanically prevented rather than merely warned against.

No result yet. Run `learn verify t4-p3-01` locally, or push to trigger CI.

artifactartifact: metrics/definitions.md
unrun
reporepo: commit_precedes
unrun