Harness Intelligence Wiki
CLIControl Plane

Control Plane Baseline Metadata

Artifact metadata shape for stable scaffold baselines

Control plane baseline metadata describes the stable scaffold baseline without transferring the archive inline.

Fields

  • Channel, currently used for stable baseline metadata.
  • Version, used for cache placement and operator evidence.
  • Manifest artifact metadata for scaffold-baseline.json.
  • Archive artifact metadata for scaffold-baseline.tgz, including URL and SHA-256.
  • Optional tag and commit metadata for traceability.

Invariants

  • Metadata is typed by packages/contract.
  • Archive downloads are checksum verified before extraction.
  • A control-plane metadata failure does not skip GitHub stable release fallback.
  • Backend artifact storage remains a later implementation concern.

Runtime Use

The metadata points the CLI at downloadable baseline artifacts. The CLI still owns archive download, checksum verification, extraction, cache placement, and fallback decisions. The API contract gives the CLI a typed source of artifact facts; it does not make the backend responsible for local scaffold rendering.

On this page