Logging and observability

Maturity: verified

The bounded application publishes structured files, not a general logging or experiment-tracker subsystem.

File

Publication

Meaning

resolved_config.sha256_<digest>.yaml

before training

complete validated application recipe

metrics.jsonl

terminal, atomic

completed optimizer-step records only

checkpoints/step_<step>.pt

at cadence/final step

model, optimizer, and lineage state

non_finite_training_error.json

non-finite failure

exact failure stage and tensor diagnostics

run_manifest.json

terminal, last

status, identities, lineage, and artifact hashes

Step records

Each JSON Lines record contains:

{
  "event_type": "optimizer_step",
  "global_step": 1,
  "loss": 0.125,
  "num_target_patches": 8,
  "sample_ids": ["sample-001"]
}

Serialization rejects non-standard non-finite JSON values. Component metrics cannot redefine application-owned event_type, global_step, or loss fields.

Terminal status

A successful manifest records status="succeeded" and final global_step. A non-finite failure records status="failed", the last completed step, failure stage, and attempted step. The manifest is the terminal inventory; the current application emits no separate lifecycle-event stream.

Provider logs remain provider-owned. The Gemini Enterprise Agent Platform submission adapter submits a job but does not collect or duplicate Cloud Logging output.

See Also