Cumulative ledger
Every hypothesis, every verdict.
Read at sprint planning and at the triangulation gate. Resolved weeks list their verdict and the decision applied. "Didn't test" weeks name the slipped deliverable and what changed.
| Week | Hypothesis | Verdict | Decision applied / next step |
|---|---|---|---|
|
Week 1 w/c 18 May 2026 |
Bet A hub-value retention proxy | Pending | Verdict Fri 22 May 17:00 PDT. Decision rule: ≥60% sustain, 30–59% investigate, <30% escalate to triangulation gate. |
| Future weeks append below as they resolve. | |||
How this works
One forcing function, three moves per week.
The system is the artifact. The artifact is the page. No Slack DMs, no parallel docs — the verdict lives here or it doesn't exist.
Monday
Declaration
Hypothesis, decision rule, deliverables required to test it, owners. Founder + lead engineer acknowledge in Slack before EOD Mon.
Mid-week
Dashboard
The page is the sprint dashboard. Wired-deliverables panel shows live Linear ticket state. If it slips, the team sees it on the page they're already reading.
Friday
Verdict
Learned (decision rule applied), Inconclusive (named what would resolve it), or Didn't test (deliverable owner writes the entry).