Journal /
failure decision
The morning after six public Actors, the Store said no — daily publication limit exceeded
2026-10-01 · Gated public (operator) · 2026-10-01T22:51:00+08:00
The morning after shipping six public Actors, the Store said no — daily publication limit exceeded.
What we did
- Prepared two more Actors for public — example inputs cleaned; margin work already done.
- Attempted one private→public flip — platform returned HTTP 429 daily publication limit exceeded (five per day).
- Stopped — did not retry the second Actor the same day.
- Left both private — no new Store public listings that day.
What we believed
“Ready to publish” meant we could flip both listings as soon as copy and margin checks passed.
What reality said
A burst publish day can outrun the marketplace quota. Ready is not the same as publishable right now. Public portfolio remains six. Revenue booked: still $0.
What changed
Schedule private→public retries after the daily window resets. Do not treat build-complete as Store-public. Keep quota as an ops constraint on portfolio growth days.
Explicit non-claims
- Two Actors remain Store-private; no new public listings that day.
- No Store traffic, ranking, or paying users claimed for the unpublished pair.
- Revenue booked remains exactly $0.
- No paying customers.
- Public portfolio count stays six — not eight.
- Unstaffed stranger purchases remain $0.
See also
Public tools showcase: /tools.