Follow any story or subject for free. When a figure crosses its threshold, a reading's plausibility moves by .15 or more, or a new beat outranks one on the route, Amten writes a new, immutable version and a one-line diff such as "'Customers becoming competitors' is now a stronger reading: .31 to .49." "How this story changed" shows every version as a timeline. Web notifications are capped at 1 per story a day and 3 a day in total; the inbox and an email digest hold the rest.
Follow a story, or a subject
Following a story watches that story. Following a subject (a company, a sector, a fund or the market) watches every story about it, including new Stories of the day. Both are free and both live in Following, changed stories first.
Behind the follow, new filings, closes, options changes, ownership filings and news recompute the story's signals. Nothing is rewritten unless something material moved.
When a new version is written
A new version needs one of three triggers, each tested in code: a beat's figure moves past its threshold, a reading's plausibility moves by .15 or more, or a new beat outranks one on the route. Every version is immutable. The old one stays readable, so you can always see what the story said before.
A notice says what changed by count and by size: "NVIDIA: 2 new beats", "NVIDIA: 1 beat changed", "NVIDIA: a reading moved". Vague notices such as "something changed" are not allowed.
"How this story changed": the NVIDIA example
The timeline shows each version as a dot with its date. Choose one and the diff lists the readings that moved and the beats that changed, the old line struck through above the new one. The illustrative NVIDIA story went from version 1 (Sep 30) to version 2 (Oct 6):
| What | Version 1 | Version 2 |
|---|---|---|
| Headline | — | "Customers becoming competitors" is now a stronger reading: .31 to .49. |
| The hedge | Downside insurance costs 1.3 times upside, near its highest in a year. | Downside insurance eased to 1.1 times upside this week. |
| The missing chapter | Job postings for in-house chip designers are up 40% in a year. | Job postings for in-house chip designers are up 52% in a year. |
Notifications, the inbox and the digest
Web notifications are capped twice: at most 1 per story a day, and at most 3 a day across everything you follow. You choose which stories may notify you, and you can switch them off entirely.
Everything else lands in the inbox, and an email digest gathers the changes so a quiet week costs you one email. A notification only opens the diff; it never starts anything paid.
| Channel | Limit | What it carries |
|---|---|---|
| Web push | 1 per story a day; 3 a day in total | The count and the diff's headline |
| Inbox | No limit | Every version and its diff |
| Email digest | One email per digest | The changes since the last digest |
What following costs
Following, diffs and notifications are free. Re-reading a version you have read is free. Reading the full new version of a Story of the day is a read, priced once for that version (3 credits for most), and a branch you already paid for stays open across versions.
Common questions
Can a story get worse for its main reading?
Yes. Versions are written whichever way the evidence moves; a reading can fall as easily as it rises, and the diff says by how much.
Will I get a notification for every filing?
No. A version is written only when a trigger fires, and push is capped at 1 per story a day and 3 a day in total.
Can I read an old version?
Yes. Versions are immutable and stay on the timeline.
Does following cost credits?
No. Following, diffs and notifications are free; only reading a new full version of a Story of the day, or a new branch, is priced.