Tenon
ES Talk to an engineer Request a pilot
Reproducibility

Published policies can be rebuilt.

From build 0.4.104 on, every Forge generation is archived with its seed, the manifest revision and scene hash it was trained on, the container digest and its gate report. With those records, any of those policies in the changelog can be rebuilt on the training node.

Seed archive

Every generation is archived by seed. The seed is stored with the generation and referenced in its deployment report.

Scene hash

Scene revisions are versioned against manifest revisions. Each scene compilation produces a hash, recorded in the deployment report since build 0.4.104.

Container digest

Training runs in NGC containers pinned by digest, starting from nvcr.io/nvidia/pytorch:26.08. The archive records the digest, not the tag.

Rebuilding a policy

  1. Read the seed, manifest revision, scene hash and container digest from the policy's deployment report.
  2. Pull the container by digest.
  3. Recompile the scene at that manifest revision and check it against the recorded scene hash.
  4. Train from the archived seed on the 8×H100 node: 90 GPU-hours, 11 hours of wall-clock.
  5. Run the gate on held-out SKUs and compare the result with the archived gate report.

The node, its orchestration and its monthly consumption are on infrastructure; manifest previews on inference.