We started tracking which AI model wrote every line, and you should too
JER@lifeofjerWe started tracking which AI model wrote every line, and you should tooWe've been building the same app for over a year with AI agents @atlas_v_erified.Not one model. Testing models, QA models, building models, design models. Frontend, backend, schema, architecture — all of it.
- ▪JER@lifeofjerWe started tracking which AI model wrote every line, and you should tooWe've been building the same app for over a year with AI agents @atlas_v_erified.Not one model.
- ▪Testing models, QA models, building models, design models.
- ▪Frontend, backend, schema, architecture — all of it.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,664 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 | X (formerly Twitter) |
| Canonical URL | https://twitter.com/lifeofjer/status/2087608101293916466 |
| Publication time | Wed, 12 Aug 2026 19:05:17 +0000 |
| Retrieval time | 2026-08-12T19:11:31.838Z |
| Last seen | 2026-08-12T19:11:31.838Z |
| 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 | mchs6zTmQ51s · 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
JER@lifeofjerWe started tracking which AI model wrote every line, and you should tooWe've been building the same app for over a year with AI agents @atlas_v_erified.Not one model. A bunch of them. Testing models, QA models, building models, design models. Frontend, backend, schema, architecture — all of it. Cursor keeps shipping new ones (theirs and other labs) and we keep trying them.And for most of that year period we had no real way to answer a pretty basic question: which model actually wrote this code or which model created this plan?We had anecdotes.Take for example Opus 4.7. Promising, but we learned after heavy use that it would say the work was done and only complete part of it. Partial implementations. We figured that out fast and moved to a different model.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at X (formerly Twitter).
Discussion
0 commentsMore from X (formerly Twitter)
