Six of 48: I logged every way my AI agents failed for five months
Six of Forty-Eight On 11 September 2026, at two in the morning, an agent told me my business had stopped selling tickets. It pulled the analytics tables, read the ad platform's numbers, wrote its report, opened a pull request, and flagged itself as urgent: no purchase had completed anywhere on the site in ten days. It named the commit it believed had broken the checkout.
- ▪Six of Forty-Eight On 11 September 2026, at two in the morning, an agent told me my business had stopped selling tickets.
- ▪It pulled the analytics tables, read the ad platform's numbers, wrote its report, opened a pull request, and flagged itself as urgent: no purchase had completed anywhere on the site in ten days.
- ▪It named the commit it believed had broken the checkout.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,117 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/taylorancapital/nothing-threw/blob/main/SIX_OF_FORTY_EIGHT.md |
| Publication time | Wed, 23 Sep 2026 13:30:56 +0000 |
| Retrieval time | 2026-09-23T13:39:30.794Z |
| Last seen | 2026-09-23T13:39:30.794Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | tC4ApNnMbPo0 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Six of Forty-Eight On 11 September 2026, at two in the morning, an agent told me my business had stopped selling tickets. It had been running unattended for weeks. It pulled the analytics tables, read the ad platform's numbers, wrote its report, opened a pull request, and flagged itself as urgent: no purchase had completed anywhere on the site in ten days. It named the commit it believed had broken the checkout. It said revenue was leaking and that resolving it needed a live check it couldn't perform itself. Two tickets had sold three days earlier. They were in the payments database, in the server logs, and in the ad platform's own pixel receipts.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.