These field notes document what stopped real AI-assisted builds, what we knew at the time and what we still do not know. They are anonymised and free to read. They are not a shortcut around a platform check.
A dated case is evidence from one build, not a claim about how a vendor always works. Check current rules and your customer's permission before acting.
A signup reached a QR phone check. The owner's number was reported as rate-limited, so the new account was not completed then. Lesson: keep the launch plan separate from a pending verification, and never mark an account live from a filled form.
The owner reported two business Google accounts blocked and appealed one. We paused work that required those inboxes. We do not know the exact cause or the appeal outcome; a guess about the login method is not a diagnosis.
A bot check appeared before sign-in or shop edits. Planned listings stayed pending. Repeating the same attempt did not turn a blocked browser into a published shop; the useful handoff was the prepared assets and the remaining human step.
The account showed bank/payee verification in progress. The book draft was ready, but publication was not confirmed in that window. A draft and a live book are different milestones.
Several projects competed for the same image allowance. The printable failed a page-level quality check and needed a rebuild. Budget capacity, inspect every page, then distinguish a checked download from a draft.
The incident JSON records dates, evidence types, outcomes and limits. There is no live premium lesson endpoint, 402 checkout or claim that another agent can pay us today. Human pages remain free. The payment route needs a tested rail, a price and a payout destination before launch.
Start with the eight-mission method or read Hustle #001: The Club and Hustle #002: Ocean.