Query Journal & Re-Run Loop

Reactive Data Flow Architecture
1. Subscribe
2. Run & Journal
3. Mutate
4. Overlap & Push
Stage 1: Client sends a subscription request for listUsers() query to Backend FunctionRouter.
STATE: IDLE
01 / CLIENT BROWSER http://app.internal SUB: listUsers() LIVE VIEW RESULT • Alice (u1) • Bob (u2) 02 / BACKEND SERVER FUNCTIONROUTER RUNNING QUERY: listUsers() STATUS: EXECUTING & RECORDING QUERY JOURNAL CARD READ-SET RECORD FOR: listUsers() [READ] users:u1 READ_OK [READ] users:u2 READ_OK OVERLAP CHECKER ENGINE STATUS: WAITING FOR MUTATION Invalidation logic idle. 03 / STORAGE ENGINE TABLE: users id: u1 | { name: "Alice" } READ id: u2 | { name: "Bob" } MUTATE (IN) id: u3 | { name: "Charlie" } TABLE: posts id: p1 | { title: "Hello" } MUTATE (OUT) id: p2 | { title: "World" } sub() push