Skip to main content
Version: MVP

Training trajectory exports

2 min readReferenceUpdated 2026-05-19

What you'll find here

The stable review-and-replay format for self-improvement loops — TrainingTrajectoryExport, the per-step decision record, redaction posture, compatibility rules, and the compressed summary form.

Review and replay, not raw trace.

Exports are designed for review and replay fixtures. They are not a raw trace dump and must not be used to reconstruct private prompts or local workspace state.

Export record

TrainingTrajectoryExport:

schema: craik.training_trajectory_export

format_version: craik.training_trajectory.v1

Task id and outcome

Ordered decisions

From runner step results.

Receipt references and redacted payloads

Evidence references and redacted payloads

Compatibility notes

Redaction paths

Per-step decision

TrainingTrajectoryDecision:

Step result id

Phase

Runner id

Status

Summary

Observed output

Diagnostics

Artifacts

Receipt ids

Evidence ids

Redaction boundary

Ids and summaries, never raw payloads.

Trajectory exports redact secret-like values, private payload fields, prompts, responses, traces, raw outputs, raw trajectories, credentials, and local-only filesystem paths. Local filesystem paths are replaced with [LOCAL_PATH]; secret-like values use the shared redaction marker.

Compatibility

Forward-compatible by default.

Consumers use format_version to select parsing behavior. Producers may add fields to the export envelope or decision records; consumers should ignore unknown fields and preserve the original format_version when forwarding an export.

Compression

TrainingTrajectorySummary compresses an export into a reviewable summary.

Source export id

Task id and outcome

Decision count

Phase and status counts

Selected redacted summary lines

Omitted decision ids

Receipt · evidence · policy envelope ids

Replay fixture & result ids

Unresolved risk ids

Compression must not remove required replay context.

Replay fixture and result ids remain top-level fields even when the decision that introduced them is omitted from the summary lines. Consumers that need full diagnostics, artifacts, observed output, or per-step timestamps must load the source export.

What's next