floatty-interactive-view

To prevent direct store mutations in interactive views, enforce a spec-driven verb surface and route all outline changes through host dispatch wiring rather than patching state directly inside door components.

Before coding interactive Floatty views, you must declare verbs in the spec, verify host dispatch wiring exists, and establish a required re-projection subscription to validate the architectural pattern.

Host dispatch wiring separates spec-defined verbs from mutation logic, ensuring interactive calendar and graph patterns route outline changes through the host rather than leaking state mutations into components.

Mutation logic leaks and regressions occur when interactive views bypass spec-defined verbs and host dispatch patterns, causing patch-stacking instead of maintaining clean architectural separation during outline mutations.

Yes, this pattern applies to any interactive view requiring drag, click-to-edit, or keyboard navigation that mutates the outline, covering kanban, tree, calendar, and graph patterns with consistent validation steps.

The best way to validate spec architecture is pre-validating the verb surface and host dispatch pattern before writing component code, ensuring re-projection subscriptions are established to reduce regressions across interactive views.