scripts/gen_compatibility_docs.py from
packages/export/sediment_export/compatibility.py. Don’t edit this page.
A canonical schema validates Sediment’s contract. A consumer profile
validates the exact boundary named here. Neither proves model quality,
task correctness, or hosted job acceptance. Profile versions don’t replace
Evidence recipe versions, canonical schema versions, or Provenance.
Validation entry points
Output artifacts
Every populated profile publishes a private directory containingdata.jsonl, evidence.jsonl, and compatibility.json. If splitting
is enabled, populated partitions use data.train.jsonl and
data.eval.jsonl, with matching evidence files. Empty partitions
produce no file. An empty export creates no destination.
The manifest records file hashes, profile identity, skip counts, split
counts, numeric Reward counts, and exact prompt overlap. The evidence
sidecar preserves canonical metadata and source hashes. It isn’t trainer
input. Publication refuses an existing destination and validates every
row before exposing the directory. Split exports reject exact prompts
shared by train and eval; semantic task overlap still needs review.
skipped counts adapter exclusions. CLI profiles preserve
canonical_skipped from their training projection; RLVR profiles also
preserve source-bundle fragmented counts. These populations stay
separate. Low-level callers omit unavailable source populations; an
explicitly supplied empty map records zero counts.
See Export for a consumer for
installation, exact commands, configuration, and consumer limitations.