Skip to content

STE-52: the full flow recorded from the live API, and a README checklist that tells the truth - #56

Merged
Lin1er merged 2 commits into
mainfrom
docs/52-d3-api-evidence
Sep 17, 2026
Merged

Lin1er merged 2 commits into
mainfrom
docs/52-d3-api-evidence

Conversation

@Lin1er

@Lin1er Lin1er commented Sep 17, 2026

Copy link
Copy Markdown
Owner

Linear: STE-52 · ACC by Axel 2026-09-17 · reviewers @axelmatsama @fable

What

  • api/scripts/d3_flow_transcript.py runs register → audit → license → use against a live deployment and writes a Markdown transcript of real requests and responses. Every claim is checked as it is written:

    • sha256(report) == evidence_hash;
    • the agent paid exactly the price;
    • has_license is true on chain;
    • the served bytes hash to the on-chain content_hash;
    • the repeat call is free;
    • a DANGEROUS version is 403 with no challenge.

    It adapts to whether the deployment requires the STE-48 ownership proof, and says which path it used.

  • docs/evidence/d3-flow-transcript-2026-09-17.md: generated against production, 15/15 checks. A fresh agent GC4NCXWO… bought cctp: settle e8a3c398…, mint 4c5960c0….

  • demo/x402-buyer/buy.js: new STOP_AFTER_PAYMENT=1 option.

  • README.md Deliverables:

    • D1 is fully ticked, per Axel.
    • D2 is fully ticked.
    • D3 items 1–2 are ticked.

    Each ticked line links to its evidence. Dashboard URL (STE-26), video (STE-28) and screenshots stay unchecked with their owner tickets.

Honesty note

The first production run failed at the payment step. I had filtered the buyer's output from my display, so the cause was not captured. The next two runs passed, and the committed transcript is from a passing run. Once production has STE-48, the transcript will be regenerated so it records the ownership-proof path.

Tests

  • ruff clean.
  • The transcript is itself the e2e against production (15/15).

…checklist that tells the truth

SOW D3 asks for proof of register -> audit -> license -> use. Criteria 1
and 2 were met, but the proof was spread over Linear comments and JSON
files, and the README Deliverables checklist had every box unchecked,
including items live for days.

- api/scripts/d3_flow_transcript.py walks the flow against a deployment
  and writes a Markdown transcript of real requests and responses. Each
  claim is checked, not printed: sha256(report) == evidence_hash, the
  agent paid exactly the price, has_license on chain, served bytes hash to
  the on-chain content_hash, the repeat call is free, and a DANGEROUS
  version is 403 with no challenge. It adapts to whether the deployment
  already requires the STE-48 ownership proof, and says which it used.
- demo/x402-buyer/buy.js gains STOP_AFTER_PAYMENT=1 so the transcript
  records the repeat call itself.
- docs/evidence/d3-flow-transcript-2026-09-17.md: generated against
  production, 15/15 checks. Fresh agent GC4NCXWO..., settlement e8a3c398,
  mint 4c5960c0.
- README: D2 all five items and D3 items 1-2 ticked, each linking its
  evidence. Dashboard URL, video and screenshots stay unchecked with their
  owner tickets. D1 is left to Axel.

Found while reviewing the transcript, filed separately: the 402
challenge advertises resource.url as http:// behind the TLS proxy.
Each line links where it can be checked: contract IDs and tx links in
docs/deployments.md, the green Contracts workflow on main. The coverage
percentage quoted on Linear is not recorded in the repo, so it is not
repeated here.
@vercel

vercel Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sterish Ready Ready Preview Sep 17, 2026 12:00pm UTC

@Lin1er
Lin1er merged commit 467f29e into main Sep 17, 2026
5 checks passed

This branch was successfully deployed

1 active deployment
Preview — b87c12f0 Deployed Sep 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant