paybondpaybond
Sign in

T06 · Tutorial

Proof and receipts

Connect signed completion evidence to portable ARS receipts — what operators and counterparties can replay.

~20 minIntermediateSandboxcommerceoperatorReceipt cards

Outcome: Name the proof objects on a successful sandbox settlement.

Learning view: objectives and extras expanded. Switch for commands only.

Mental model

Release is proof-gated: signed evidence drives settlement; receipts are portable claims, not log screenshots.

You will be able to

  • Name authorization, completion evidence, and settlement receipt fields
  • Locate proof in :9477 timeline, CLI table, or hosted replay
  • State capture amounts come only from validated evidence

Prerequisites

  • · A green sandbox smoke or middleware execute once
  • · Familiarity with integer cents and cost_and_completion

Proof is first-class

Kit’s public promise is proof-gated release and portable receipts. After a successful sandbox settlement you can point at concrete artifacts — not screenshots of logs. The proof gate evaluates signed evidence; receipts are the portable claims you inspect in Console and hand to counterparties.

Authorization

Operation
travel.book_hotel
Requested ceiling
20000 cents ($200.00)
Decision
spend_authorized

Shown on the authorize phase of middleware trace.

Completion evidence

Preset
cost_and_completion
Reported cost
18700 cents ($187.00)
Intent
intent-… (session-bound)

cost_and_completion resizes capture to validated cost.

Settlement receipt

Status
released
Captured
$187.00
Unused release
$13.00

Amount derived only from validated, signed evidence.

Inspect the same artifacts from CLI

  1. Step 1 of 2

    Table trace for a run

    Headless-friendly authorize → evidence view after multi-step or smoke with a run-id.

    Goal: Confirm resize-to-evidence without opening a browser.

    Run this

    paybond agent run trace --run-id <run-id> --format table

    Example response

    PHASE       OP                  RESULT
authorize   travel.book_hotel   ok · ceiling 20000
evidence    cost_and_completion released · 18700
settle      captured $187.00 · residual $13.00

    You should see: Table shows authorize allow and evidence released (or spend_denied).

  2. Step 2 of 2

    Local timeline dashboard

    Second terminal in the project that wrote .paybond/dev-trace.jsonl.

    Goal: Map card fields to authorize / evidence / settle phases on :9477.

    Run this

    paybond dev trace

    Example response

    Trace UI listening on http://127.0.0.1:9477
Serving .paybond/dev-trace.jsonl

    You should see: Browser at :9477 shows authorize then evidence for the last smoke.

    Note: Hosted replay (no local server): /demo/agent-trace.

Where to inspect

  • Local dashboard: paybond dev trace → :9477
  • CLI: paybond agent run trace --run-id … --format table
  • Hosted: /demo/agent-trace and interactive Proof Lab at /demo
  • Console (authenticated): operations intent dossier

Standard & docs

Verify before you continue

Check these off against your terminal or timeline output — progress stays on this device.

0/3

If something goes wrong

  • If you see

    Trying to override capture amount after evidence

    Do this

    Settlement amount is derived only from validated, signed evidence — callers cannot force larger captures.

  • If you see

    Treating model text as proof

    Do this

    Proof is signed completion evidence evaluated by the proof gate, then receipt objects — not chat transcripts.

Self-check

Answer without scrolling up — then reveal the model answer to compare.

If cost_cents is lower than the authorized ceiling, which value should the settlement capture, and why?

Next steps

Pick a branch — not every path needs every tutorial.

Related docs & recipes

Recipes are copy-paste production smokes — not repeated inside this tutorial.