Own the loop that improves your models.

Harbor runs post-training work inside your environment. It observes each candidate and the infrastructure carrying it, recovers failed jobs, applies your evaluation gates, and returns a decision record for human sign-off.

Representative experiment recordPolicy-bound
  1. 01Observe

    Read run state, model signals, cluster health, and approved new work.

  2. 02Plan

    Turn the experiment contract into candidate jobs, policies, and evaluation work.

  3. 03Execute

    Run training and evaluation jobs on infrastructure inside the customer environment.

  4. 04Intervene

    Recover infrastructure failures, restore checkpoints, or prune a bad trajectory.

  5. 05Evaluate

    Invoke the customer evaluation harness and apply task, safety, and latency gates.

  6. 06Decide

    Return an accepted candidate and complete operations record for human sign-off.

Human approvalAccepted work can begin the next approved cycle

The loop works because it can stop.

Autonomy is defined in policy, not implied by the word operator. The inspected implementation can recommend actions or operate within policy, while deployment remains gated on a person.

Experiment policy

Mode
Operate within policy
Infrastructure retries
Enabled, maximum 2
Bad-run pruning
Enabled
Before deployment
Human sign-off required
Experiment #428support-agent-v17Illustrative record from the reference implementation
Candidate APrunedLoss trajectory violated policy
Candidate BAcceptedRecovered from checkpoint, then passed all gates
Candidate CRejectedSafety gate blocked promotion

One record from proposed work to promotion.

The operator coordinates the systems already responsible for training, infrastructure state, checkpoints, evaluation, and identity. Harbor adds the decision logic and the durable operating record between them.

Observe

See the model run and the machines carrying it.

Harbor reads experiment state beside Kubernetes, Slurm, DCGM, NCCL, Prometheus, and run metrics. The operator can distinguish a bad training trajectory from an infrastructure fault because both are in the same record.

  • Candidate state and loss
  • Rank and collective health
  • GPU and scheduler evidence
Operate

Keep controlled work moving when infrastructure fails.

The reference operator identifies a failed GPU, quarantines its node, validates the last checkpoint, rebuilds the training allocation, and resumes the candidate. Every action is written to an actor-attributed operations log.

  • Policy-scoped actions
  • Checkpoint verification
  • Recorded recovery receipts
Evaluate

Make the promotion decision from your own gates.

Harbor invokes the customer evaluation command, applies blocking criteria, and returns the accepted and rejected candidates with evidence. The implementation keeps deployment behind a required human sign-off.

  • Customer eval harness
  • Blocking safety policy
  • Human promotion approval

The reliability engine stays inside the operating boundary.

The reference implementation keeps training data, checkpoints, and model weights local. Harbor connects with scoped permissions to the systems that observe jobs, execute approved actions, store state, and run evaluations.

Customer environmentExperiment jobs only
ObserveDCGM · Kubernetes · Slurm · NCCL · Prometheus
OperateScoped Kubernetes RBAC · Slurm submit/cancel
StateLocal data · checkpoint store · model registry
JudgeCustomer eval command · isolated eval pool · gate policy

AI Infrastructure Operator

Keep the work, evidence, and promotion decision in your hands.