System DesignSLW fleet rivent.dev →

Now

What's in flight in System Design. Updated by every session that changes it.

In flight

Recently landed

Next

Initiatives

SLW Data Engine — spine build brief (workstream: engine)

PR #1 merged, service deployed (Shawn ran the Vercel deploy), and the FULL ambiguous band is assessed — 1,264/1,264 links carry an AI verdict. The Ledger review-queue UI is built ([PR #2](https://github.com/SKO70SV/slw-webster/pull/2), awaiting merge + deploy).**_

You are the **engine** workstream session. You build the spine of the SLW Data Engine. Work autonomously; this brief defines scope, rules, checkers, and stop points. When in doubt, the rules win over speed.

Ford classification and handoff

Shaping — scope needs cutting down before any build

The intelligence flow is mapped, verified and shipped. This initiative covers the specific gaps Shawn named on the 2026-08-04 call that the shipped pipelines do not yet handle — how material gets classified on the way in, and how a company Ford learns about surfaces in the books that already own it.

How research becomes coordinated knowledge across the fleet: Ford's three ingestion doors, Terminal and Podcast publishing their durable residue, and the Webster entity spine coordinating companies & VCs across DealFlow and LP Flow, with Dewey as the shared document substrate underneath.

Propose and decide — the front half of the review loop

Mockup up for review — Michael driving, waiting on Shawn's placement call

Everything we have built for reviewing work operates on changes that already exist as code. Nothing operates on a proposal before the code exists. This initiative adds that front half: propose a design, discuss it, decide — then hand off to the lane that already works.

Edit this page·History