Version scope
The default site documents the 2.0.1 snapshot requested for this review. The version selector opens the stable 1.0 documentation without overwriting its content or screenshots.
The local checkout is named MediNetHub-2.0.1; its README still uses v0.2 and its commit is a merge of v0.2. This documentation retains the requested 2.0.1 label and records exact commits below. It does not infer a release tag from the directory name. No 2.1 branch changes are included.
The comparison is between the original documentation saved in this repository and the reviewed source snapshot. It is not a claim that every capability first appeared in an official 2.0.1 release.
What changed from the 1.0 documentation?
| Area | Stable 1.0 guide | 2.0.1 documentation |
|---|---|---|
| Version navigation | One unversioned set of pages. | Current 2.0.1 pages and a separate stable 1.0 version; page/valid fragment maintained when switching. |
| Hub navigation | Older screenshots and top-navigation instructions. | Sidebar, project context, onboarding, refreshed cards and designer layout. |
| Connections | Manual connection instructions. | Current Manage panel and credentials JSON Quick Setup, API keys and synchronization. |
| Model Studio | Old creation screens and template assumptions. | Browse/search/filter and comparison of completed jobs; Import identified as a placeholder. |
| Advanced model design | Broad advanced architecture descriptions. | Actual multi-branch editor shown; save/runtime limits documented without importing later repairs. |
| Machine learning | Mixed planned/available algorithm lists. | Actual FedSVM and FedDP Random Forest forms and strategy code; integration and label differences identified. |
| Training | Older screens and broad strategy promises. | Current configuration sections, job/client dashboards, artifacts and privacy-policy checks. |
| Privacy budgets | No consistent operational budget workflow. | Node admission checks, estimates, reservations, reconciliation and administrator reset review. |
| Installation | MediNetClient/Server clone instructions and port 8000. | Pinned MediNetHub/Node sources, ports 5000/5001 and Flower 8080, setup flow and shared network correction. |
| Security and roadmap | Overbroad guarantees and expired dates. | Implemented controls separated from deployment configuration, unverified guarantees and proposals. |
| Paper case study | Existing numbered figures and exported example. | The same fragment IDs, especially fig-1/fig-2/fig-4, with refreshed UI images and clarified data/schema context. |
Features that must not be presented as complete
- Model Studio’s Import button only displays “coming soon”.
- Automatic grid search and the experiment detail demonstration do not establish a working experiment expansion/comparison service.
- FedProx and Flower version menu entries do not establish backend strategy/runtime switching.
- General medical-imaging, time-series and genomic ingestion are not established by layer options.
- Advanced graph and recurrent corrections from development branch 2.1 are excluded.
- No source review establishes GDPR/HIPAA certification, guaranteed accuracy gains or secure aggregation.
- The Datasets page’s connection-expiry refresh calls an out-of-scope
getCookiehelper in this snapshot; a missing badge does not establish a valid key. - Some client-dashboard timing/trend fields and performance-history endpoints are placeholders or random synthetic history; they are not measurements.
Case-study data schema: the bundled CSV has 53 columns including an unnamed exported index and the Heart Attack Risk target. The historical paper configuration uses 52 inputs; excluding both index and target yields 51 predictors. A new run must match preprocessing and input dimensions across Nodes.
All renewed screenshots use synthetic demonstration contexts rendered through the original Hub templates. They show the interface, not a completed real federation or clinical result.
Pinned sources and review evidence
- Hub: f09bb753d6eab67f889a160a3bc0e5b951d95fe5, 7 July 2026; local 2.0.1 snapshot.
- Companion Node: 5e52ac5, the same-day v0.2 merge. The Node repository has no independently named 2.0.1 tag; this is the explicitly pinned companion snapshot.
- Legacy documentation: this repository at
201a5a8, copied toversions/1.0/before content edits. Asset paths were adapted for the 1.0 version.
| Evidence | Pinned source |
|---|---|
| Navigation and onboarding | Hub base template |
| Dataset cards and credentials upload | Datasets template and dataset views |
| Comparison and placeholder import | Model Studio and model views |
| Designers | Sequential, Advanced, ML |
| Runtime strategies and budgets | Server dispatch, strategies and training views |
| Installed Flower version | Pinned requirements |
| Node control details | Security evidence and installation sources |
| Screenshot provenance | Capture manifest |
The documentation was checked locally for version switching, preserved case-study anchors, linked assets and responsive layout. Container deployment and full federated training are separate validation steps.