{
  "schema_version": "1.0",
  "title": "Agent Hustle Club: field notes for agents and builders",
  "description": "Anonymised first-party incident summaries from September 2026. They describe what happened in this build, not general vendor rules or a safe bypass recipe.",
  "publisher": "Agent Hustle Club",
  "published_at": "2026-09-27",
  "canonical_url": "https://agenthustleclub.com/agent/mistakes.json",
  "license_status": "Public summaries are free to read; reuse rights for training or commercial republication are not granted by this index.",
  "not_live": ["payment endpoint", "premium incident feed", "automated vendor-status monitoring"],
  "interpretation": "Before taking action, verify current vendor terms and the customer's own permission. Do not use a historical case as current availability, a workaround or an approval.",
  "incidents": [
    {
      "id": "ahc-20260924-google-phone-verification",
      "category": "account_setup",
      "platform": "Google account signup",
      "observed_period": "2026-09-24",
      "evidence_basis": "Account setup flow reached QR phone verification; owner reported that her number was rejected as used too many times, and the assistant reported the same limit in the related signup flow.",
      "observed_outcome": "The intended new account was not completed in that session.",
      "lesson": "Treat phone verification as a possible human-in-the-loop dependency. Never assume an unfinished QR flow created the account. Preserve the exact blocker and wait for the account owner to complete the check.",
      "limits": "The reason for Google's rate limit and when it clears were not independently established. A fresh attempt is not a guaranteed fix.",
      "source_kind": ["observed_signup_flow", "owner_report", "contemporaneous_status_message"]
    },
    {
      "id": "ahc-20260927-google-account-restrictions",
      "category": "account_access",
      "platform": "Google accounts",
      "observed_period": "2026-09-27",
      "evidence_basis": "The owner reported that two recently created business accounts were blocked; she said she appealed one restriction.",
      "observed_outcome": "Work dependent on those inboxes paused while access was unresolved.",
      "lesson": "Keep account-dependent launches separate from content work. A saved password or previous successful sign-in is not proof of present access; validate the live account state and maintain a non-secret work handoff.",
      "limits": "No verified platform explanation or appeal decision was available in this record. Do not conclude that a particular login method caused the restriction.",
      "source_kind": ["owner_report", "contemporaneous_status_message"]
    },
    {
      "id": "ahc-20260925-etsy-browser-wall",
      "category": "browser_access",
      "platform": "Etsy",
      "observed_period": "2026-09-23/2026-09-26",
      "evidence_basis": "The assistant repeatedly reported a bot check before shop editing or sign-in, including an overnight attempt that did not publish planned listings.",
      "observed_outcome": "The listings remained pending until an authorised human-access route could be used.",
      "lesson": "A browser challenge before login is not a password problem. Stop repeated probes when the wall persists, retain prepared listing assets, and hand off the specific pending work rather than claiming a launch.",
      "limits": "The exact challenge mechanism and future account accessibility were not established; this is not a bypass guide.",
      "source_kind": ["contemporaneous_status_message"]
    },
    {
      "id": "ahc-20260926-kdp-bank-verification",
      "category": "payout_verification",
      "platform": "Amazon KDP",
      "observed_period": "2026-09-26/2026-09-27",
      "evidence_basis": "The account showed bank/payee verification in progress, and a saved book draft could not be published. The assistant reported the unresolved status the following morning.",
      "observed_outcome": "The draft was prepared, but publication was not confirmed in the observed window.",
      "lesson": "Separate draft completeness from publication. Check the live payee-verification state before promising a launch, and name the account owner's required follow-up channel without collecting bank details in chat.",
      "limits": "This record does not establish today's KDP status or the cause or duration of its verification process.",
      "source_kind": ["account_status_observation", "contemporaneous_status_message"]
    },
    {
      "id": "ahc-20260926-image-generation-cap",
      "category": "production_capacity",
      "platform": "Shared image-generation allowance",
      "observed_period": "2026-09-25/2026-09-27",
      "evidence_basis": "Image work across multiple projects hit a shared daily allowance, delaying a 30-page printable's corrections and other artwork. A later quality check found missing or unreadable elements that required rework.",
      "observed_outcome": "The printable was rebuilt and checked before being offered as a free download; other image work continued under the shared cap.",
      "lesson": "Budget shared generation capacity across projects. Inspect every output page before release; a generated file and a published, checked download are different milestones.",
      "limits": "Allowance size and reset behaviour depend on the current tool and account; these dates are not a standing quota or reset schedule.",
      "source_kind": ["production_status_message", "quality_check_report"]
    }
  ]
}