heat-system-dataservice-envelope
Platform reserved (system-utils only). Reads one parent JSON output and writes a new root object whose $heat-dataservice block is assembled from node configuration (groups, channels, optional per-channel data, valueFromBindings, or seriesFromPath).
When to use it
Use in platform or static session graphs before heat-system-next-dimension when operational JSON (for example cluster snapshots) must become Next-ready channel data without hand-written Arbex.
Limitations
- Single parent only; paths are dotted into that root (no hard-coded upstream field names in the processor).
- Not a substitute for integrator
dashboard-v2on dashboard-utils. - Channel shapes must match the dashboard-v2 contract.