Concepts
Live Queries
Live queries reuse the same browser query object for initial fetch, updates, invalidation, and authorization.
Kizaki live queries are query-centered:
- build a query object in the browser
- fetch it once or subscribe to it live
- let the platform apply the same read policy model to both
Why This Model Is Simpler
In many frontend stacks, realtime introduces a second client architecture with different primitives, different authorization assumptions, and a separate cache story. Kizaki tries to avoid that split.
The query object is the anchor:
- it defines what the UI wants to read
- it can be fetched once
- it can be kept live
- it stays subject to the same authorization model
This keeps the browser model close to the read model you would already write without realtime.
What Developers Should Internalize
The main value of this design is not just convenience. It is coherence:
- one read model
- one authorization model
- one browser mental model
That coherence is what lets realtime feel like a normal part of application development instead of a special subsystem that infects everything else.