Lifecycle And Messaging Flow
guarded state transitions, rollback rules, and hub publication paths
Dark SVG source uses the VMx architecture palette and keeps arrows behind masked component boxes.
State semantics
- Destructed is the fresh-builder start, Constructed is the ready state, and Disposed is terminal.
- Reconstruct is not shorthand in docs: it is its own observable four-step sequence.
- Rollback after failed hooks is part of the normative lifecycle contract.
Atomicity
- A per-VM guard serializes lifecycle work and blocks concurrent re-entry.
- Late async completions that race dispose() abort instead of reviving a torn-down VM.
- Container VMs orchestrate children but do not change the core state machine.
Messaging
- Hub messages remain the cross-VM coordination surface.
- Per-instance propertyChanged surfaces exist so views do not need to filter the shared hub when they bind one VM.
- Collection and tree messages extend the same hot-stream model for containers and recursive trees.