Downstream · draft, not for sending as-is

For the systems-design read

Hey [name],

Lawmaking is the one high-stakes system in the country that still runs open-loop, and I'm building the instrumentation for it.

A memorandum carries essentially the same legal force as an executive order, and it can set rule-writing and money in motion with no statute anywhere upstream. That is why the archive runs first and the forecasting comes later. A forecast only means something against a record someone else can check, and today no institution keeps that record. What exists now is the record half: a daily archive sealed with a hash chain, a Federal Register digest every business day, the presidential corpus, a House floor radar with sponsorship joins, and an MCP server so other people's machines read the same record people do. Forecasting does not exist yet, and every consequence claim we've drafted is still held back as unverified. That is the design, not a backlog.

This is a systems pitch, so break it like one. The work-in-progress deck is at https://seedownstream.com/deck/. Tell me where the map of the machine is wrong and which loop I've missed. And if the machine grabs you, let's talk.