// reproducible local output

Artifact to release to deployment, captured from the current tree.

This page shows real output captured on 2026-07-07 from a named command in this repository. It starts a local plaintext development brain, registers two demo endpoints, then drives dona artifact, release, and deploy commands against it.

Run it yourself How it works

fresh capture

Deployment pipeline transcript

The ids and ports below are expected to change on each run. The shape is the point: a CI artifact becomes an immutable release, then a deployment record with durable events and canary strategy state.

Captured: 2026-07-07T10:41:59Z UTC
Command: website/scripts/capture-deployment-demo.sh

$ dona --control 127.0.0.1:7270 status demo.greeter
service demo.greeter (config v2)
  endpoints:
    127.0.0.1:40589        variant=v1   region=us-east
    127.0.0.1:44207        variant=v2   region=us-east
  weights:
    v1     100%

$ dona --control 127.0.0.1:7270 artifact register ...
artifact registered: artifact-demo.greeter-sha256-0123456789abc-1783420922954094911 service=demo.greeter image=registry.local/demo/greeter:v2 digest=sha256:0123456789abcdef signature_verified=false

$ dona --control 127.0.0.1:7270 release create --artifact artifact-demo.greeter-sha256-0123456789abc-1783420922954094911 ...
release created: release-demo.greeter-v2-1783420922959087037 service=demo.greeter version=v2

$ dona --control 127.0.0.1:7270 deploy start --release release-demo.greeter-v2-1783420922959087037 --env prod --strategy canary --stable v1 --canary v2 --steps 50,100 --manual
deployment deployment-demo.greeter-prod-1783420922964890829 status=Running updated=1783420922
  release: release-demo.greeter-v2-1783420922959087037 service=demo.greeter version=v2 commit=0123456789abcdef
  environment: prod driver=bare-metal target=prod
  strategy: canary stable=v1 canary=v2 steps=[50, 100]
  detail: deployment started
  events: 2

$ dona --control 127.0.0.1:7270 deploy events deployment-demo.greeter-prod-1783420922964890829
deployment deployment-demo.greeter-prod-1783420922964890829 status=Running updated=1783420922
  release: release-demo.greeter-v2-1783420922959087037 service=demo.greeter version=v2 commit=0123456789abcdef
  environment: prod driver=bare-metal target=prod
  strategy: canary stable=v1 canary=v2 steps=[50, 100]
  detail: advanced canary v2 to 50%
  events: 3
  1783420922 Created        status=Pending     actor=ci deployment created
  1783420922 Started        status=Running     actor=ci rollout started
  1783420922 StepAdvanced   status=Running     actor=controller advanced canary v2 to 50%

$ dona --control 127.0.0.1:7270 deploy list --service demo.greeter --env prod
deployment deployment-demo.greeter-prod-1783420922964890829 status=Running updated=1783420922
  release: release-demo.greeter-v2-1783420922959087037 service=demo.greeter version=v2 commit=0123456789abcdef
  environment: prod driver=bare-metal target=prod
  strategy: canary stable=v1 canary=v2 steps=[50, 100]
  detail: advanced canary v2 to 50%
  events: 3

reproduce

The named command

Re-run the transcript from the repository root:

cd /home/code/proj/dona
CARGO_TARGET_DIR=/tmp/dona-target website/scripts/capture-deployment-demo.sh

The script only creates local temporary data directories and local processes. The hey.ad cluster was decommissioned on 2026-07-13; this command does not contact any hosted deployment or create cloud resources.

observe status

No observe explorer transcript is available yet

BP-04's persistent observe service exists as a gRPC ingest/query API with memory and ClickHouse-backed stores, spool handling, and tests. The browser/CLI explorer output requested by the blueprint is not an available runnable surface in this tree, so this page uses the deployment pipeline transcript above instead of inventing explorer output.

The classic progressive-delivery walkthrough is still reproducible from the Rust workspace:

cd /home/code/proj/dona/rust
CARGO_TARGET_DIR=/tmp/dona-target ./demo.sh