Skip to main content

Alpha release contract

Covenant alpha releases are source-built local infrastructure releases. They provide a reproducible daemon, CLI, policy, memory, audit, provenance, and workflow substrate for inspection and extension. They are not binary distribution releases, SDK stability commitments, or public signing events.

Boundary

  • Builds from source on supported developer hosts.
  • Uses the documented validation profile for local control-plane surfaces.
  • Records live-test prerequisites instead of hiding skipped boundaries.
  • Keeps distributed settlement, installers, SDK publication, release-scope and audit-root signing, and transparency publication as planned work until implemented.

Evidence bundle

Public alpha candidates surface against the validation profile below. The readiness report, bundle scaffold, and bundle validator that produce the recorded evidence currently live in engineering-loop tooling and are not part of the public scripts directory.

bash agent-os/scripts/validate.sh --quick node agent-os/scripts/provenance.mjs verify-all pnpm --dir landing build git diff --check

Accepted bundles require alpha readiness to be clear. Draft blocker review can use an explicit blocked-readiness override without turning that draft into accepted release evidence.

Human-owned decisions

Release id, tag creation, artifact upload, signing workflow access (branch protection rules), and public announcement language remain human-owned until the project has explicit automation policy and neutral project credentials.

Related