The Unified Action Console — ONE Agency on one side, the Operator Mesh on the other, and every packet of work crossing between them lands here. Console prototype: the intake and queue are real in this browser; the server organs (the /api endpoint, the watching daemon) belong to the back-end build.
ONE Agency — Timmy's side of the bridge. Advertiser intake and business-side routing: local businesses in, creators matched, deals closed.
Open ONE Agency →Operator Mesh — Wade's side of the bridge. The workforce engine: jobs posted, operators claiming, work moving. On the Meadow today, the mesh runs on the ONE Job board.
Open ONE Job (the Mesh) →The contract every packet crosses with, per Jang's schema task. The "sapp" field ships under the name Jang gave it — its definition is his to supply.
Jang's design turns on an event loop that watches for new work and fires packets. In this prototype the watcher is local: it logs every landing and routing, in the open.
Fill the intake and fire it across the bridge. The packet lands in the queue below, stamped and inspectable as JSON.
Packets and the watcher log live in one blob in this browser. Export it to move it, import it to restore it.