All documentation

Reproduce a regression, then check your project

Run the offline broken/fixed starter, inspect your source scope, and record a technical pilot.

In this guide

See what the check catches

The integration starter runs two real viem requests against a local transport. The broken path drops the Builder Code; the fixed path uses the official ox helper. Doctor and the captured calldata must agree. No wallet, RPC endpoint, keys, or funds are needed.

Run the starter commands from the BAO Toolkit checkout with pnpm 9.15.4 and Node 20.11 or later. For your own app, use the released CLI 0.6.0 commands below.

pnpm install --frozen-lockfile pnpm --filter @base-attribution-os/integration-starter... build pnpm --filter @base-attribution-os/integration-starter demo pnpm verify:integration

Preview the policy for your own app

Point the released CLI at your application and supply your registered Builder Code. Review the paths, findings, config, and pinned workflow in the preview. Remove --dry-run to create the files. Existing workflows are preserved even with --force.

Use --include for your actual transaction source directories. No supported paths means coverage is not measured. Init success means the files were created; the strict Doctor check determines whether findings block CI.

pnpm dlx @base-attribution-os/cli@0.6.0 init --path /path/to/app --builder-code bc_yourcode --workflow --dry-run pnpm dlx @base-attribution-os/cli@0.6.0 init --path /path/to/app --builder-code bc_yourcode --workflow pnpm dlx @base-attribution-os/cli@0.6.0 doctor --path /path/to/app --profile strict

Record the result of the integration

Save separate before and after reports outside your Git repository. Each records tool versions, commit and dirty state, code, scope, and per-path findings. A report with findings is saved before the command exits 1.

Attach an existing Proof Set with --proof-set and a CI run URL with --ci-run when available. Source coverage and sampled transaction evidence stay separate. The summary does not contact RPC or verify the supplied CI link.

pnpm dlx @base-attribution-os/cli@0.6.0 pilot-report --path /path/to/app --output /private/pilot/before.json pnpm dlx @base-attribution-os/cli@0.6.0 pilot-report --path /path/to/app --format markdown --output /private/pilot/after.md

Try a technical pilot with BAO

Bring one TypeScript transaction path, exact client versions, and a public reproduction. A useful pilot ends with a finding your team confirms, an accepted fix, and a check retained in CI. Share only evidence you intend to make public.

The starter and reference projects are maintained by BAO. They are reproduction material, not evidence of independent adoption.

Read the maintained source reference