Rule 3 of 8 · Chapter I — Component Discipline
Pick the hosting model per application, not per fashion.
Why this rule exists
Server gives you latency-sensitive simplicity, WASM gives you offline and scale-out for free, and Auto gives you both complexities at once. Each is right somewhere; none is right everywhere.
In practice
Interactive Server for internal, chatty, always-online tools. WASM for public apps that must scale or work offline. Choose per app and write the choice down.