KV Spec Format

ByteOr pipeline specs use a deterministic key-value text format. This page is the public-hub index into the canonical OSS format reference rather than a second copy of that reference.

What Matters At A Glance

  • Specs are emitted as deterministic UTF-8 key=value lines.
  • Stable ordering means the same logical spec hashes to the same bytes.
  • The format is intentionally diff-friendly and canonicalizable.
  • Exact field names, model shapes, and validation-aligned structure should come from the OSS reference docs.

Canonical Published Surfaces

Example Shape

pipeline.name=example
pipeline.target=SingleRing
pipeline.stages.0.id=stage-a
pipeline.stages.1.id=stage-b
pipeline.constraints.shards=1
Provenance
Need the canonical source?
Use the public hub to orient yourself, then jump to repo-owned docs or rustdoc when you need contract-level detail.