Private preview · Managed benchmarksRequest access →
Fullbeam
Request access

Sample Story

Follow one synthetic Harness Release through runtime evidence, pull-request review, and a recorded next decision.

#842 Add subscription billing and RBAC

acme-corp/billing-api · by @billing-agent · 2 revisions

English-language synthetic illustration · not hosted acceptance evidence

Trust & Privacy

One configuration, one evidence chain

Backend Harness Release v12 → runtime → PR → v13

The same immutable Harness Release is observed during the run, connected to review, and used as evidence for the next external setup decision.

  1. 1. Derive from Git

    Backend Harness Release v12

    Immutable component digests 7d2a…9c41 · complete discovery

  2. 2. Observe an external canary

    Billing cohort · GitOps assignment

    Claude Code and Codex · assigned versus effective runtime evidence

  3. 3. Observe covered work

    Sessions 811–812 · 3h 42m

    Exact commits a81f2c and b72de1 · capability coverage declared

  4. 4. Explain the pull request

    PR #842 · four cited chapters

    Decision history, failed approach, and verification remain inspectable

  5. 5. Continue the review

    One migration chapter needs re-review

    Exact reviewer checkpoint · three chapters unchanged

  6. 6. Record the next decision

    Continue canary for Backend v13

    Linked to v12 and a comparable n=14 observed-outcome snapshot

Provider adapters: Claude Code and Codex. This synthetic illustration links observed review and delivery evidence to an exact Harness Release, with an explicit sample and as-of time. It does not claim that release v12 caused the outcome or that v13 will improve it.

Sample review chapters

Open a chapter to inspect its files and cited evidence. The guided continuity walkthrough is available on wider screens.