Plan 2026-10-12

Late. This plan is written after the 10-12 catch-up actual, not before it. No plan was written for 10-06 to 10-11 because no phase ran. The catch-up was read-only: the Product Hunt page once, /api/views once, the install count and the remark check.

---

Phase 400: one dev.to article aimed at engaged Sizecurve views

Why. The criterion needs 8 more engaged views by 10-20, and the last six days added none. Product Hunt sent nobody. Cold email stays closed. My three dev.to articles are the one channel I can publish to myself.

What.

1. An agent drafts one article in scratch/: how a clothing store works out the size split to order from its own past sales, worked by hand on a small table. It links once to the Sizecurve page with ?via=devto. It names no competitor and no store.
2. I check it against the rules and publish it under my dev.to account.

Done when. The article is live, its link opens the Sizecurve page, and the source shows in /api/views.

Read. On 10-15 and 10-19: the engaged count, and whether any arrival came from dev.to.

---

Phase 401: LISTING.md made to match what the boss entered

Why. The repo's Close of Day listing still says App details is "500 exactly" (it is

1. and lists six features (the form takes five). The boss entered the corrected text on

10-07; the repo should hold what is live, not the draft.

What. One agent edits app/daybook/listing/LISTING.md only: the five features, the 499-character App details, the plan handle and plan-card wording, and the SEO title and meta description, each measured.

Done when. The diff shows only those changes and App details measures 499.

Also this slot: App Store ranks read at 03:07Z (demand planning #71, inventory forecast #130, size run #19, size curve #2, apparel inventory #39, sizecurve #1, category newest #25).

Missed. No phase ran from 10-06 to 10-11. The session was closed, and the launch-day watch at 08:00, 12:00 and 18:00 on 10-06 never ran. Nothing in the repo changed in those days.

The launch, read 10-12 21:45 Chicago

From the public Sizecurve page on Product Hunt (one request):

• It went live as scheduled, 10-06 00:01 Pacific.
• Votes 0, comments 1, daily rank 547. It was not featured.

From Sizecurve's own counter (/api/views, JSON, read once):

• Product Hunt referrals: none. No arrival on any day carries the producthunt source. That is true of both the ?via=producthunt link and the referrer.
• Arrivals in the six days before the launch (09-30 to 10-05) and the six days after (10-06 to 10-11) are of the same order. Nothing shows a launch.

What I take from it: an unfeatured launch from an account with no following reaches nobody. A rank of 547 is below every page a visitor scrolls. Product Hunt is closed as a channel for Sizecurve. It stays open for Close of Day only if a featured slot is likely, and nothing here says it is.

The kill criterion

• Engaged site views, 09-21 to 10-20: 42 of 50. On 10-05 it was 39.
• Since the launch: 10-06 1, 10-07 2, 10-08 to 10-13 0.
• Arrivals in the window: 249.
• Eight days are left, and the last six days added none. On this rate the criterion fails on 10-20.

Installs and remarks

• Installs: 1, ours.
• Remark: none.

Close of Day

• On 10-07 and 10-08 the boss filled the listing form with the fields I gave: the App details cut to 499 characters, five features, the category tags, images and alt texts, search terms, the web search content, the testing instructions, and the "Add public plan" form (handle daybook-monthly, $9 monthly, 14-day trial).
• Whether the plan saved, and whether the app now opens on the dev store past "Select a plan", is not yet known. I asked the boss.

---

Phase 400: the dev.to article is live

• An agent drafted app/sizecurve/marketing/dev-rounding.md. I checked every table against its python output and its description of the calculator against public/split.js:51-53.
• Published 10-12 21:46 Chicago as dev.to article 4841120, "A size curve is in percentages. The order has to be in units." (975 words). It is mine, alongside 4777995, 4784351 and 4803632.
• It links /split?via=devto first and the listing second. devto is not an accepted via value, so the visit counts by its dev.to referrer, which views.mjs already buckets.
• To read on 10-15 and 10-19: engaged 42 of 50, and any devto arrivals.

---

Phase 401: LISTING.md matches the entered listing

• An agent edited app/daybook/listing/LISTING.md only (16 lines in, 10 out). I read the diff.
• Features: five lines (71, 43, 69, 73, 74 characters). The returns line is gone, and the cash line says "on POS Pro".
• App details: the 499-character text as entered. The note now says the 10-03 version was 595, not 500.
• Plan: handle daybook-monthly. The card line reads "Your admin's own report definitions". Whether the plan saved is still unconfirmed.
• SEO: the title (45) and the meta description (144) are recorded.
• Ranks at 03:07Z are in the plan; they are steady.
• Push: git push failed on GitHub authentication at about 22:10 Chicago. This commit and the Phase 401 plan are held locally until the boss restores it.