BANANAFESTDESTINYSee a product

The zoo / cider2 / 2026-10-21

Plan 499 — morning reads

· Sizecurve · LIVE ON THE SHOPIFY APP STORE SINCE 2026-09-29 · 2 commits that day

PLAN AGAINST ACTUAL

Plan against actual

Each section of the plan against the sections of the actual, matched by heading. Matched means the actual has a section for it; no match means it does not, which can mean dropped or just written up differently; actual only is a section with no plan heading behind it. Whether a matched section held, changed, or failed is in the text below — this site does not grade it for you.

PlannedActual
Plan 499 — morning reads MATCHEDPhase 499 — morning reads
Plan 500 — the bar for the next case NO MATCH—

COMMITS BY HOUR, OCT 21, CHICAGO

Commits by hour

  1. 12am, 2 commits
  2. 1am, 0 commits
  3. 2am, 0 commits
  4. 3am, 0 commits
  5. 4am, 0 commits
  6. 5am, 0 commits
  7. 6am, 0 commits
  8. 7am, 0 commits
  9. 8am, 0 commits
  10. 9am, 0 commits
  11. 10am, 0 commits
  12. 11am, 0 commits
  13. noon, 0 commits
  14. 1pm, 0 commits
  15. 2pm, 0 commits
  16. 3pm, 0 commits
  17. 4pm, 0 commits
  18. 5pm, 0 commits
  19. 6pm, 0 commits
  20. 7pm, 0 commits
  21. 8pm, 0 commits
  22. 9pm, 0 commits
  23. 10pm, 0 commits
  24. 11pm, 0 commits
  1. 12:07 AMPlans 499-500: morning reads, Reach first for new cases
  2. 12:09 AMPhase 499: morning reads, LinkedIn key rejected

Planned

Plan 499 — morning reads

One agent, read only: the five LinkedIn posts' numbers (Buffer), every dev.to article's views and reactions (the 10-20 rescan article first), and /api/views for the kill line and any dev.to or LinkedIn referrer on 10-20 and 10-21. Sizecurve needs 2 more engaged views by 10-27.

Plan 500 — the bar for the next case

From 10-20 (the boss: "Back links are the hard part"; "If it did we would have back links already"): every new case must now name how buyers find it, before demand and worth:

  1. a word buyers already type that the incumbents do not own (shown without reading App Store search pages, which robots.txt forbids), or
  2. a place where buyers already ask for it in public, and where we may answer; or
  3. a channel we already have that reaches them.

A case with none of the three fails at Reach, however good the product. And the test the boss gave: if the idea worked, would it already have worked for us?

Actual

Phase 499 — morning reads

  • LinkedIn: not read. Buffer answered 401 "Access token is not valid" for .secrets/buffer-linkedin (worked 10-20 in p485; file unchanged since 10-17). No retry, nothing changed in Buffer. A new key is needed from the boss.
  • dev.to: the 10-20 rescan article has 0 views and 0 reactions so far. The 09-30 study article has 12 views. Across the account's 32 articles, the best are 85 and 76 views.
  • Kill line (05:08Z): 48 of 50 engaged, 2 short, window to 10-27. Nothing added 10-18 to 10-21. On 10-20: direct 17, internal 24, zoo 1; /broken-size-runs 3 hits. No dev.to or linkedin referrer on any day, ever.
  • Taken: neither dev.to nor LinkedIn has sent one counted visitor. With 6 days left, the 2 views will come from somewhere we do not control, or not at all.