Documentation guide
Start at the repository README for the CPU quickstart, workflow selection and current results. This index covers the complete recipe collection. Run examples from the repository root and use fresh output paths. Individual guides specify which optional environment and hardware their commands require. The programme status provides the implementation/gaps map; the environment framework comparison explains OpenEnv, NeMo Gym and the difference between a harness and a resource server.
Learn and run
The generic training fixtures verify integration. The German SFT and agent-RL guides contain the actual local-model experiments. Gym qualification has its own evidence; Lightning and native Prime-RL GPU training are separate, unqualified paths. A validated trajectory file is not automatically a trainer input.
Evidence and current status
- Current validation overview: software checks, hardware runs,
practical limits and repeat commands. Its linked validation.json describes the historical foundation, rather than the later GPU experiments.
aggregate JSON: matched MGSM outcomes, language/format inspection, resource use and saved artifacts.
aggregate JSON: strict tool-workflow outcomes, mathematical retention regression and full provenance.
aggregate validation: native CPU checks plus the NeMo Gym A100 update qualification, without a new held-out quality claim.
- Roadmap and acceptance criteria: remaining quality, partner
adoption, benchmark, service, domain and publication work.
Full data, model outputs, adapters and weights live in ignored runs/ directories; they are not downloaded by opening this documentation or cloning the repository. The results name their local artifact directories and model cards. Reproduction requires access to the documented model/data sources and suitable hardware.
Programme, infrastructure and publication
| Element | Reference | Current boundary |
|---|---|---|
| Architecture and provenance | Architecture | Common configuration/evidence contracts with upstream optimization and environment backends. |
| Academic and industrial related work | Reuse map | Adopted components, integration pins, candidate systems and research extensions. |
| Two open benchmarks | Proposed designs and existing benchmarks, development tracks | German RAG with cited evidence and business-communication agent sequences are the proposed topics; current fixtures remain plumbing, with expert data/scorers and released benchmarks still pending. |
| Evaluation kit → service | Remaining service work, roadmap | Local kit exists; managed service execution has not been built. |
| Robotics, Bio/Med and materials | Domain sketches | Native model/tool choices and proposed metrics; no domain implementation or container qualification. |
| Cluster and containers | Operations | Recorded Determined A100 runs; Dockerfile and Slurm script remain examples needing separate qualification. |
| Hugging Face candidate bundles | Release guide | Local checksummed packaging and review material, with no automatic Hub uploads. |
| Hugging Face recipe home | Layout, institutional examples and source mirror | Private personal Static Space with upstream links; our weights, data and raw run artifacts remain on the cluster. |
| hessian.AI organization and artifact cards | Organization profile draft, model card, dataset card | Drafts/templates; namespace, authority and publication terms remain to be established. |
The initial delivery excludes JUPITER work. General multi-GPU/multi-node support, scientific benchmark validity and deployment readiness require separate evidence. Use the validation level actually demonstrated when describing any recipe.
