Design session capture. Cameron's mandate: general systems, not special cases — message passing where Dana is a subset, devices whose processing cycles you own, and money modeled as the flows it actually is (who pays Marcus; where the Lab's revenue comes from; the accounting stream you tap, siphon, and cook).
ADOPTED AS LAW (new constitution section 'The flow law: signals, messages, money'):
- The world is nodes exchanging flows over three graphs — signals (devices), messages (social), money (accounts) — sharing three player verbs everywhere: tap, inject, redirect.
- Message latency decided general: delivery on the recipient's clock and channel (closes the intel.md [OPEN] proposal).
- Ownership grants cycles: an owned device contributes processing capacity and hosts resident automations (reach.md extended).
- Filings are messages: the detection reporting pipeline becomes interceptable message traffic; every aggregate-observer.md criterion preserved — only the carrier changes.
NEW SPECS (both READY):
- spec/messages.md — channels with read conditions, delivery on recipient schedule, authored per-person traffic (Marcus's 3 a.m. call is phone traffic), typed information payloads, filings-as-messages, taps feeding the intel buffer.
- spec/economy.md — the Lab's account graph (revenue/payroll/procurement on the day clock), tap/inject/redirect for money, income routes (siphon/cook books, sell information, small stock+goods positions), legitimate expansion from trust (the Lab grows your hardware with its own money), Marcus's debt payable from slush or by payroll intervention. Resolves the B1 money-income blocker.
ROADMAP: #17 messages + #18 economy; flow-law chain sequencing #15 reach -> #14 cursor -> #16 intel -> #17 messages -> #18 economy as the single red lane.
Also restores three DEVLOG ledger entries (presence-is-a-cursor, cursor-implications, intel-record-and-process) that were dropped in today's merge-queue conflict resolutions — union rule.
Docs only; no code change.