the-vm-standard

To enforce a standardized View Model architecture in TypeScript, apply a single-file VM definition convention using the {ComponentName}.vm.ts naming pattern. This ensures file naming, tagging, and layer exports remain consistent across your codebase.

The best way to separate business logic from View Models is to prohibit logic inside the VM and delegate it to services. View Models should solely expose reactive UI bindings, ensuring proper separation of concerns.

To set up live and test variants for View Models, use a canonical Layer structure with namespace import patterns. The default export must use VMRuntime.key to export both live and test variants for reliable testing and production readiness.

Yes, the View Model standard requires single-file VM definitions to prevent divergence in VM definitions. Each View Model must reside in a single file named {ComponentName}.vm.ts, enforcing a uniform pattern for atom usage and tagging.

View Models need namespace imports and atom naming conventions to maintain consistency and proper separation of concerns across UI-related code. This uniform pattern enables reliable testing and prevents architectural divergence across teams.