Execution API

Maturity: verified

Execution APIs define how callers start a unit of work and inspect its result without making provider lifecycle part of the application contract.

Pretraining interfaces

The current surface executes one bounded pretraining attempt and provides its checkpoint and evidence helpers.

Application lifecycle

Symbol	Contract
PretrainAttemptContext	caller-supplied run, attempt, repository, mount, and optional provider provenance
run_pretraining_attempt	execute exactly one bounded attempt and publish its terminal evidence
PretrainAttemptRecord	successful attempt identities, artifact URIs, final step, and loss

Checkpoints and evidence

Symbol	Contract
TrainingCheckpointMetadata	strict completed-step and lineage identity
save_training_checkpoint	save native module and optimizer state plus metadata
load_training_checkpoint	validate exact structure and caller policy before state restore
optimizer_step_metric	create one collision-checked completed-step record
write_metrics	atomically publish strict JSON Lines metrics

The caller owns retry and provider lifecycle. The application and these helpers do not implement validation, epochs, best-model selection, distributed state, or exact random-number-generator resume.

See Also

• Training loop

• Checkpoint format

• Storage layout