The flow law: signals, messages, money — spec/messages.md + spec/economy.md master
Cameron's mandate: general systems, not special cases — Dana-replies-at- her-desk must be a subset of a message system, a camera is a computer whose cycles you own, and money must be modeled as the flows it actually is (who pays Marcus, where the Lab's revenue comes from, the accounting stream you tap and siphon). Adopted as constitutional law: the world is nodes exchanging flows over three graphs (signals / messages / money) sharing three player verbs — tap, inject, redirect. New spec/messages.md (READY): channels with read conditions, delivery on the recipient's clock, authored per-person traffic, typed information payloads, filings-as-messages with aggregate-observer criteria preserved. New spec/economy.md (READY): the Lab's account graph on the day clock, tap/inject/redirect for money, income routes (siphon, sell information, small positions), legitimate expansion from trust, Marcus's debt payable both ways. Resolves the B1 money-income blocker (old ROADMAP #17). Amendments: intel.md message-latency proposal closed as decided-general; reach.md ownership grants processing cycles; detection.md filings-are- messages contract note; markets.md named as economy.md's B3 scale-up. ROADMAP: #17 messages, #18 economy, flow-law chain sequencing. Docs only — implementation dispatches via the chain #15 -> #14 -> #16 -> Defense: constitution rule — the amendment is the decision; code follows by dispatch. The flow law is the self-similar-scale clause applied to flows instead of things: the same tap/inject/redirect interface must serve five people in a basement and a planetary economy, which is also why it satisfies scale-native social systems and markets-as-schemes without new machinery. Filings-as-messages honors the aggregate-observer law by changing only the carrier, never the accumulate/decay behavior.