This device

The engine makes no network calls. The Worker that owns this database contains no fetch, no XMLHttpRequest, no WebSocket, no importScripts and no sendBeacon — zero of each, counted in the source and held at zero by a test. Nothing in the browser forbids a Worker from opening a socket, so this is a fact about what the engine does, not a cage it sits in; the test is what keeps it true.

Four routes outside it can send something out, and each only when you act. Every one writes to the log below as it goes.

What the log does not cover: the queries this app makes to read when you are signed in — checking your session, listing worlds and exports, counting an agent's pending proposals. Those send a request and receive rows back; they carry no world content outward, and they are not written down below. So the log accounts for everything that goes out, not for every packet.

• world/feed.ts Reads the public feed, and writes back two things: that an item was opened here, and the situation INDEX — titles, bands and entity keys, never an account or a reading (F0.2). Runs when you: Pull feed · Open a situation · Sync
• world/sync.ts Writes to the coordination plane, and can upload the exported SQLite file — the whole world, and the largest thing that can leave this device. Runs when you: publishing or adopting an export
• components/StudyGateB.svelte The owner opens the exact hosted draft, then sends only the Gate-B outcome, reviewed decision ids, and a publish request for that bound draft. It never mints a run, sends a new intake, or uploads the local document. Runs when you: reviewing and publishing a formal Study
• world/client.ts Writes the exported SQLite file to your disk. No server is involved — but the world does leave the app, so it is logged like anything else that goes. Runs when you: exporting or downloading the world