VMx System Architecture

spec 3.25.0 source of truth -> catalog-complete flavors -> host examples

VMx System Architecture spec 3.25.0 source of truth -> catalog-complete flavors -> host examples VMx System Architecture spec 3.25.0 source of truth -> catalog-complete flavors -> host examples Specification control plane Core runtime surface Support contracts and helpers Flavor implementations Example and validation loop spec/ 24 chapters 138 ADRs VERSION 3.25.0 fixtures 4 JSON fixtures lifecycle + hubs commands + derived 12-conformance 407 library IDs 5 THEME scenario IDs 412 total Lifecycle base ComponentVMBase guarded transitions dispose cascade VM families component + composite group + aggregate shared collection + move Commands RelayCommand decorators ModeledCrudCommands Capabilities 22 micro-interfaces selection / CRUD / paging opt-in behavior Services MessageHub Dispatcher IDialogService ILocalizer Collections + state lists + VMCollection DerivedProperty SearchableState AsyncResourceVM Paging primitives PagedComposition TokenPagedComposition filtered ordering Notifications INotificationHub NotificationVM ConfirmationVM C# PascalCase surface System.Reactive NuGet packages Python snake_case surface reactivex uv + pytest TypeScript camelCase surface rxjs dual ESM/CJS Swift camelCase surface Combine SwiftPM resources Rust Rust type names VMx-owned facade Cargo crate Compatibility matrix independent versions manual spec mapping spec-major tracking Four flagship hosts C# + Python + TypeScript + Swift Five flavor packages C# + Python + TypeScript + Swift + Rust Flagship examples Notes Workspace across four hosts 19 feature rows + THEME-001..005 CI gates spec-discipline coverage tool examples contract checks Release posture shared normative concepts idiomatic per language repo facts drive docs norms catalogues injected into coordinates idiomatic APIs versioned separately hosts enforces documents

Source of truth

  • Behavior changes start in spec/ and flow through fixtures and conformance IDs.
  • The lifecycle table, message ordering, and command truth table are shared repo facts.
  • The docs diagrams mirror the same structure rather than invent a parallel model.

Parity shape

  • Five flavors implement one normative conceptual runtime with idiomatic public naming.
  • Reactive primitives stay native per flavor; Rust uses the VMx-owned hot-stream facade.
  • All five flavors align on canonical public concepts; the completed Rust ledger records focused evidence.

Examples and gates

  • The flagship Notes Workspace exercises 19 framework features plus THEME scenarios.
  • Coverage, spec discipline, and example checks keep docs claims tied to repository state.
  • Compatibility and release surfaces are versioned per flavor but tracked against the spec.