A device-fleet inventory at the cluster level. The network plugins, sensors, industrial controllers, and edge appliances the platform manages get a unified registry with capabilities, vendor metadata, and per-device configuration. Plugged into the operator GUI as a fleet view. The operations team gets one screen for what the cluster is talking to, not a scatter of per-plugin dashboards.
Next patch
An operations team running Eldric in production accumulates devices over time: the firewall sending audit logs in, the UPS reporting power state, the building-automation sensors feeding the dream cycle, the manufacturing controllers wired to the policy loop. Each one ships as a plugin; each plugin has its own config UI, its own per-device list, its own credentials.
That's fine for two or three plugins. It becomes a problem at ten plugins managing 200 devices — nobody can answer the question “what is the cluster talking to right now?” without walking through every plugin's settings page.
The device registry is a kernel-level table: every plugin that manages devices declares them to the registry instead of (or in addition to) keeping its own internal list. The platform aggregates the entries into one fleet view with shared columns: vendor, model, role, location, last-seen, health, configuration delta from baseline.
This page updates as each piece lands. The release notes are the formal cut.
For the platform's plugin extension story, see plugins and networking plugins. For the IoT story, see xLSTM for IoT. For the full 5.0.x roadmap, see what's next in 5.0.x.