Documentation Map

Current frozen system · HydroCore-v5 · v0.2.1 · source snapshot 4bbf6fa3ff9f

The final HydroSwarm submission serves the frozen HydroCore-v5 system. Start with the path that matches your review goal; historical V3/V4/M9/M10 material is preserved but never overrides Final system.

New reader / domain expert path

Executive summary → Scientific evidence → Authority and safety

Read this first if you are new to the project or reviewing it from a water-infrastructure or general technical background. It explains the problem, the system, the final results, and the limitations without requiring any other document.

Judge skim path

Top-level README → Scientific evidence → Judging evidence map

This path answers: what is the system, what did the one-time final test measure, and where is the proof?

Technical reviewer path

Technical brief → Final system → Architecture → Authority and safety → Scientific evidence

Use this path to verify serving identity, learned/runtime/authority boundaries, failure behavior, and final evidence.

Scientific reviewer path

Model card → Evaluation → Dataset card → Reproducibility → Claims and evidence

Use this path to audit supervision scope, split governance, final lock, synthetic-data limits, and exact claim wording.

Operator path

Quickstart → Operator guide → Limitations

For V5, run the published docker-compose.release.yml image (ghcr.io/insightlabs38-pixel/hydroswarm:v0.2.1) or build/run the current source; both serve the same frozen V5 identity.

Core current documentation

• Executive summary
• Final system authority
• Scientific evidence dossier
• Authority and safety
• Architecture
• Model card
• Evaluation protocol and final evidence
• Dataset card
• Data generation and governance
• Reproducibility
• Claims and evidence ledger
• Technical brief
• Installation
• Quickstart
• Operator guide
• Limitations
• Glossary
• Judging evidence map
• References
• AI-assistance disclosure
• Architecture diagrams
• Security policy

Demo / product documentation

• Reference incident — workflow demonstration, not final V5 benchmark evidence.
• Problem and product boundary
• Devpost submission copy
• Final video narration/script
• Video and caption materials

The submission artifacts above mirror the frozen v0.2.1 submission story and are not scientific authorities.

Historical research

Historical records remain available for transparency:

V4 / capability-remediation era

• reports/results/v4/
• docs/evaluation/
• historical V4 release bundle under models/hydrocore-v4-release/
• V4 architecture diagram

Statements in those artifacts that the V5 lock was not yet opened are historical in time; current V5 lock status is M11.6 PASS.

V5 development milestones before final lock

• reports/evaluation/hydrocore-v5/m9* — architecture/training/capacity search
• reports/evaluation/hydrocore-v5/m10/ — downstream authority/full trajectories/serving freeze
• reports/evaluation/hydrocore-v5/m11/ — finalist freeze, full validation, one-time final lock

M9/M10 are current V5 research lineage but development evidence, not the final test.

Earlier S/M/L generation

• reports/results/medium-evaluation-final.json
• reports/results/topology-transfer-m.json
• Evaluation historical section

These results are not current V5 claims.

One rule for conflicts

If current prose conflicts with immutable artifacts, the generated frozen artifacts win. Open a documentation defect rather than averaging, guessing, or silently choosing the more favorable number.