Learn / From declarations to the screen

What is derived, and what remains explicit

ConcernDerived automaticallyDeclared explicitly
Fields and valuesEntity id, field schemas, and relationsDomain definitions and database table bindings
Query impactPredicate and order field dependenciesLoaded pages, server-only filters, live transport
Single-row writesInput schema, updated fields, when checkCustom multi-row handlers and server permissions
Selected dataVisited store entries reused by identityRelations resolved at runtime from store rows
UI regionsReused drawings when inputs hold identityExplicit path dependencies on Projection.derive
Distributed editsCommitted base plus pending local editsJournal, 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 Write or invalidate affected queries explicitly.
  • Fine-grained DOM patches: Views do not compile to per-binding DOM patches; use SlotView.region and Projection.derive (with verify in development) to isolate expensive subtrees cleanly.

Next