The revised workspace, API v2 and Node privacy-budget workflows are already in the reviewed snapshots. Future work is listed separately, with no unverified delivery dates.
Pinned implementation, not a branch roadmap
This 2.0.1 guide uses the Hub snapshot f09bb753 and the companion Node snapshot 5e52ac5, merged on 7 July 2026. The Node repository has no independently named 2.0.1 tag; these instructions pin the reviewed commits. See the version comparison for scope and sources.
The v1 roadmap mixed future ideas, implemented features and dated targets. This edition moves verified features into “Available in this snapshot” and identifies future work from the pinned repository documents. The stable v1 roadmap preserves the earlier plan.
A planned item below means it was documented as future work; it does not assert that development is currently active or promise a release date.
Features that should no longer be presented as future-only
The Hub contains the revised researcher workspace and separate model-design workflows. Route or interface availability is not a guarantee that every architecture is executable end to end.
The companion Node includes setup, dataset administration, training permissions and separate user roles. These are part of the documented hospital workflow.
The Node exposes API v2 helpers, protects production-job admission locally and supports administrator-reviewed budget resets.
Node API v2 · Admission and experiment checks · Spend reconciliation
Documented priorities without an asserted release date
The pinned Hub README lists templates and additional training parameters as future features. Individual optimizer controls already exist; a complete template library and scheduler/callback workflow are not established by that list.
Server TLS certificates are generated in Docker. Client-certificate verification remains a separate security item in the Node README. Network restrictions are a deployment requirement while that gap remains.
The Node task list records further accounting and operations work. Existing round metrics and final cost reconciliation should not be confused with a durable debit after every round.
Historical plans can lag behind the source
The pinned Hub README still describes the designer as sequential-only, although the source also contains an advanced-designer route. The Node's earlier v2 technical notes describe SVM support-vector export and simple budget checks; the pinned code instead implements DP-SGD FedSVM weights and in-flight budget admission. This documentation follows the reviewed code and labels unverified future work explicitly.
Hub routes · Current companion FedSVM · Current budget checks
No target quarters from the v1 page are carried forward as current commitments. Later branch 2.1 graph and recurrent-model changes are outside this 2.0.1 edition.
Use the guide for this snapshot