A quick map of what landed in the run-up to 5.0 GA. Grouped by area, with pointers to the feature pages that go deeper. If something on this list is unclear, write to office@eldric.ai and we'll add detail.
A lighter-weight build of the platform now ships alongside the full distribution. eldric-aios-minimal includes only the kernel, controller, data, edge and knowledge modules — about a quarter the disk and memory footprint of the full release. Intended for branch offices, kiosk boxes, Raspberry Pi-class hardware, and small VPS instances that proxy chat traffic to a larger cluster.
What changes for you: on small edge hosts, install eldric-aios-minimal instead of eldric-aios. Science, training, NOVA, swarm, comm, media and IIoT modules stay on the data-centre nodes; the edge proxies up to them. Documentation: features § Edge.
The Edge server now proxies xLSTM workload requests (policy / forecast / encode / retrieve) to the appropriate eldric-xlstmd worker. Path translation handles /v1/eldric/<workload>/... → /api/v1/<workload>/..., capability headers thread through from the cluster secret, and the worker registry refreshes every 30 seconds from the controller. Least-connections selection across multiple xLSTM workers. WebSocket upgrades pass through unmodified.
Three new Dockerfiles for ARM targets shipped this wave: Raspberry Pi 4, generic ARM64 server, and NVIDIA Jetson. deploy-rpm-fanout.sh classifies aarch64 from the filename so heterogeneous clusters install the right architecture automatically.
Every kernel endpoint is now gated by an explicit capability rather than a role string. The capability set is fixed in the binary; tenant admins compose customer-named roles from those capabilities (Pro+ feature, ships in 5.1). On 5.0, the existing four roles (Viewer / Developer / Admin / SuperAdmin) map onto the capability set under the hood. No flow changes for end users.
What this means for integrations: 403 responses now carry a required_capability field in the JSON body that tells you what was missing. Your client should surface that field; the existing chat-shell does. Webhook-subscriber and plugin authors should respect the same field on inbound responses. Reference: api-reference.md §3 Authentication.
On a fresh install, the very first signup becomes the system administrator automatically. No shipped default password. The chat shell shows a first-run card with email + password + an "I will be the administrator" confirmation. Subsequent signups land as regular users in the default tenant. Public-host warning preserved: on internet-reachable clusters, disable open signup from the Admin Console immediately after claiming the admin role.
Internal-CA management and Let's-Encrypt ACME flows are now wired through the chat shell. Generate certificates, deploy them, rotate them, request and renew Let's-Encrypt certificates — all from the Admin Console. Documentation: features §13.4.
The federated-learning round orchestration ships in the controller-broadcast + worker-train + shard-aggregate pattern. Cluster dormancy (the "idle for N minutes" tier downgrade that frees worker capacity for batch jobs) is wired through the controller. Both are off by default; admins opt in per tenant. Tracking notes on the features catalogue.
The iOS app now exposes a bottom-sheet slash-command autocomplete that mirrors the macOS GUI's slash-menu behaviour. Type / and the available commands appear; tap to insert. The Experiment Designer (UI-SPEC §6.2) renders an inline status card for science experiments — phases, sub-tasks, output links — and accepts both stub {type,id} arrivals and full payloads without an async fetch round-trip.
Sessions now carry a projectId; the sidebar filters by the current UserContext project. Knowledge bases gained a projectId selector filter and scope-parse logic — the chat header KB selector lists only KBs scoped to the active project.
The macOS GUI uses Sparkle for in-app updates. The appcast lives at https://repo.eldric.ai/5.0/macos/appcast.xml. Update channels are stable (default) and beta (opt-in via the GUI's settings).
Pre-trained ENRN classifiers and EMM matrix-memory seeds now ship through the package server alongside the platform RPM, DEB and PKG. Pin to a specific version (enrn-intent-v1), or follow the latest within a family. The installer handles the download and checksum verification.
A stress-test harness ships with 5.0 — parallel-user × request-count load runs with pass/fail thresholds against p99 latency and error budget. Verified on our demo cluster as part of the GA cut.
The 5.0 GA smoke suite runs 106 checks against a clean cluster. The current baseline holds at 93 green — the open items pair with the WIP markers in the features catalogue (xLSTM daemon cold-start, parallel knowledge-base search at concurrency 4); none block GA.
A new .nexus bundle format ships in 5.0 as admin tooling. Pack the matrix memory, vector documents, knowledge-base sources and tenant configuration of one Eldric installation into a single signed file; ship it; unpack on the other side with a clean merge. Useful for tenant portability, project handoff between teams, seeding an edge install with a tested baseline, lightweight federation between regional clusters, and disaster recovery. The bundle is scope-filtered, so a project-level export never carries other tenants' data with it.
Today on 5.0, four built-in roles (Viewer / Developer / Admin / SuperAdmin) gate the platform. In 5.1, tenant admins compose their own roles from the underlying permission set — name them anything ("Auditor", "Lab tech", "Finance"), scope them to the tenant, grant them to users. On migration, every existing superadmin keeps full access via a default per-tenant "Admin" role; everyone else starts with the explicit grants you give them.
What's shipped in 5.0 GA, what's deferred to 5.1, and what's explicitly out of scope are catalogued together. The features catalogue carries the same picture in long form, with WIP markers on the items that ship in 5.1.
For the long-form catalogue of everything that's in 5.0, read features. To install today, start at get started. To apply the platform to your own domain, read apply Eldric to your domain.