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

TopicGuideExecutable examples and inputs
Evaluation kit and regression checksEvaluationCore CLI, development specifications, real CPU generation smoke.
Existing evaluator SDKInspect integrationInspect task/scorer, dependency snapshot.
Reasoning adaptationTrainingSFT recipe, GRPO recipe, CPU trainer smoke.
Offline sequence distillationTeacher generation and filteringGeneration recipe, teacher-sequence fixtures.
German Qwen SFTEnd-to-end use caseData notes, data preparation, pilot driver.
German Qwen multi-turn RLAgent-RL use caseBounded environment/verifier, pilot driver, verified summary tool.
Native NeMo GymGym setup and TRL bridgeResource server, service smoke, client smoke, online trainer.
Longer NeMo Gym experimentFrozen protocol and recoveryExperiment driver, sealed native checkpoints, DEV selection and final assessment; the 20 October GPU resume attempt failed its token audit. Fresh JAIF plans and qualification are required.
Matched native OpenEnv experimentProtocol, tutorial compatibility and sequencingSDK client, training bridge, experiment driver, native service and sequential queue controller. CPU-qualified; the 20 October GPU resume attempt failed its token audit. No longer-run quality result is available.
Native Prime Intellect VerifiersVerifiers setupLoadable environment, explicit scripted smoke, dependency pins.
An existing team's harnessTrajectory contract and adoptionCallable example, Agent Lightning recipe, optional launcher.
LoRA checkpoint mergingMerge guideExplicit local base/adapter merge.

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

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.

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

ElementReferenceCurrent boundary
Architecture and provenanceArchitectureCommon configuration/evidence contracts with upstream optimization and environment backends.
Academic and industrial related workReuse mapAdopted components, integration pins, candidate systems and research extensions.
Two open benchmarksProposed designs and existing benchmarks, development tracksGerman 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 → serviceRemaining service work, roadmapLocal kit exists; managed service execution has not been built.
Robotics, Bio/Med and materialsDomain sketchesNative model/tool choices and proposed metrics; no domain implementation or container qualification.
Cluster and containersOperationsRecorded Determined A100 runs; Dockerfile and Slurm script remain examples needing separate qualification.
Hugging Face candidate bundlesRelease guideLocal checksummed packaging and review material, with no automatic Hub uploads.
Hugging Face recipe homeLayout, institutional examples and source mirrorPrivate personal Static Space with upstream links; our weights, data and raw run artifacts remain on the cluster.
hessian.AI organization and artifact cardsOrganization profile draft, model card, dataset cardDrafts/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.