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, signed artifacts, and transparency publication as planned work until implemented.

Evidence bundle

Each candidate should record the evidence helper output, validation outcomes, sanitized alpha readiness blockers, skipped live prerequisites, provenance links, audit-root attestations when present, and the release decision.

node agent-os/scripts/alpha-release-readiness.mjs node agent-os/scripts/alpha-release-bundle.mjs v0.1.0-alpha.1 node agent-os/scripts/alpha-release-validate-bundle.mjs v0.1.0-alpha.1 node agent-os/scripts/validate-alpha-release-evidence.mjs bash agent-os/scripts/validate.sh --quick 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, project signing keys, key rotation, and public announcement language remain human-owned until the project has explicit automation policy and neutral project credentials.

Related