Most feature surfaces should be authored as data rather than shipped as bespoke React pages. The client owns the primitive renderer and adaptive controls. The server owns semantics, authorization, command bindings, and state patches.

repository definition -> runtime UI document -> client slot renderer

Use source code for reusable primitives:

  • frames
  • tables
  • action collections
  • modal shells
  • slot renderers
  • command dispatch plumbing

Use authored data for feature composition:

  • panel layout
  • labels
  • action groups
  • data bindings
  • runtime command names
  • event-specific screens