Learn / From declarations to the screen
What is derived, and what remains explicit
| Concern | Derived automatically | Declared explicitly |
|---|---|---|
| Fields and values | Entity id, field schemas, and relations | Domain definitions and database table bindings |
| Query impact | Predicate and order field dependencies | Loaded pages, server-only filters, live transport |
| Single-row writes | Input schema, updated fields, when check | Custom multi-row handlers and server permissions |
| Selected data | Visited store entries reused by identity | Relations resolved at runtime from store rows |
| UI regions | Reused drawings when inputs hold identity | Explicit path dependencies on Projection.derive |
| Distributed edits | Committed base plus pending local edits | Journal, transport, and conflict policy |
Two explicit boundaries apply today:
- Custom server handlers: A multi-row server handler's side effects are not inferred automatically; declare single-row mutations with
Writeor invalidate affected queries explicitly. - Fine-grained DOM patches: Views do not compile to per-binding DOM patches; use
SlotView.regionandProjection.derive(withverifyin development) to isolate expensive subtrees cleanly.
Next
- Learn how
Messages and structural seams keep state consistent: Who changes application state, and how - Define your own entities, relations, and invariants: One domain declaration
- Explore server queries, caching, and optimistic writes: Remote