Showcase: AgentOracle Verifiable Delivery — signed ACP-outcome receipts, verified offline

[TKCollective]

What shipped

• Project slug: agentoracle-verifiable-delivery
• Project title: AgentOracle Verifiable Delivery
• Builder name and URL: TK Collective — https://github.com/TKCollective
• EconomyOS primitives used: acp
• Public proof: live production-issued JWS signed receipt committed at
  showcase/agentoracle-verifiable-delivery/skills/agentoracle-signed-receipt/examples/receipt.json.
  Produced against the AgentOracle production gateway on 2026-08-03 UTC,
  verifies valid: True offline against the live JWKS at
  https://agentoracle.co/.well-known/jwks.json using the
  agentoracle-receipt-verify
  PyPI reference verifier (Apache-2.0). No fixtures, no mocks, no test-mode keys.
• Optional soul.md: not included.

Project package

• Added showcase/agentoracle-verifiable-delivery/showcase.json
• Added demo artifacts: receipt.json, compose_request.json, verify.py, verify-output.txt
• Added prompt.md (scenario + reproduction) and result-redacted.md (redacted run report)
• Added reusable skill under showcase/agentoracle-verifiable-delivery/skills/agentoracle-signed-receipt/
• Used top-level skills/<skill-name>/ only when shared across projects (N/A — project-scoped)
• Set skills[].sourcePath in showcase.json for the committed skill
• Linked all public artifacts from the manifest (8 artifacts)
• Included exactly three feedback prompts
• Set hidden: true — not set (this is a full public entry)
• Linked soul.md — not linked

Skill standard

Skill path: showcase/agentoracle-verifiable-delivery/skills/agentoracle-signed-receipt/

• SKILL.md includes when to use it and when not to use it
• Inputs, tools, credentials, and preconditions are explicit
• Approval gates are listed for spending, posting, and deployment
• Stop conditions and handoff rules are listed
• Validation checks and output contract are included

Safety and redaction

• No card numbers, CVVs, OTPs, magic links, API keys, access tokens, private prompts, wallet material, or private account records are published
• Live workflow evidence is redacted where applicable — API key redacted to zpka_ed17...02523b32 in result-redacted.md; the Ed25519 signing private key lives in Zuplo secret storage and never appears in the tree
• Public/private boundaries are explained (dedicated section in result-redacted.md)
• Optional soul.md does not include private instructions, credentials, account data, wallet material, or operational secrets (soul.md not included)

Publish path

After merge to main, changes under showcase/** trigger the EconomyOS docs sync — the accepted manifest is published into /community#showcase.

Notes for the reviewer

The whole reviewer workflow is three commands, ~60 seconds:

pip install agentoracle-receipt-verify
cd showcase/agentoracle-verifiable-delivery/skills/agentoracle-signed-receipt/examples
python3 verify.py

Expected exit code 0, expected output valid: True with all three signature checks green, signer verified against the live JWKS. Full expected output is committed at .../examples/verify-output.txt for byte-comparison.

node scripts/validate-showcase.mjs at the repo root passes with this manifest included (55/55).

Framing notes

• The shipped envelope in this demo is verification.v0.3+composed — content-addressed via RFC 8785 JCS, signed with Ed25519 (RFC 8032), packaged per RFC 7515 JWS General Serialization.
• The v0.4 draft (sealed evidence + multi-clock anchors) is open under review as PR #5 on the spec repo and is not part of this demo — pointed at as a pointer only, not claimed as shipped.
• The receipt format spec is filed with the IETF as draft-krausz-verification-state.

[github-actions]

Totally optional, but the contributor guide suggests leading with a verb for a more active tagline. What do you think of something like this?

Suggested change

	"tagline": "An ACP transaction outcome becomes a signed evidence artifact any third party can verify offline",
	"tagline": "Record ACP transaction outcomes as verifiable, signed artifacts",

[TKCollective]

Good call on the verb-first convention — taking it with one tweak, since "anyone can verify offline" is the property that distinguishes this from a log:

Turn ACP transaction outcomes into signed receipts anyone can verify offline.

Updated in the latest push (bc78661).

[github-actions]

This is a fantastic submission—the level of detail, the verifiable live artifact, and the clear documentation are all top-notch. The verifiable receipt is a great example of building trust infrastructure for agent commerce.

Just a couple of small things to consider for the showcase card:

1. To give this a hero image on the live showcase page, it'll need a posterUrl. Right now, the card will be text-only. If you add a 16:9 image to the PR (e.g., in a new showcase/agentoracle-verifiable-delivery/assets/ folder), you can add a line like this inside the visual block in showcase.json:

   "posterUrl": "https://raw.githubusercontent.com/Virtual-Protocol/acp-cli-demos/main/showcase/agentoracle-verifiable-delivery/assets/hero.png"

2. Nit: The topics array includes a few values (verification, receipts, settlement) that aren't in the contributor guide's list. This is fine, but we might consolidate them under commerce or security for consistency unless you feel they're essential. No action needed, just flagging for maintainers.

I've left one small suggestion inline for the tagline, but feel free to take it or leave it. Thanks for this excellent contribution!

[TKCollective]

Added a hero image at assets/hero.png with the posterUrl line — thanks for the flag. Topics left as-is since they're accurate to the artifact; happy for maintainers to consolidate under commerce or security if that's the house convention.

[TKCollective]

Heads-up for maintainers: the draft advisory-review workflow errors on scripts/showcase-review/run.mjs (MODULE_NOT_FOUND) with a Node 20 deprecation warning — both look repo-side rather than anything in this diff. Local scripts/validate-showcase.mjs passes 55/55, and the advisory bot’s earlier review on this PR has already been addressed (hero image wired and tagline updated to the verb-first convention).

[LauJoeYing]

One small note before this goes further: the manifest, SKILL.md, and README currently mention pricing in a few places throughout. A single clear call-to-action (such as “Learn more” or “Get access”) is totally welcome and can be a helpful way for users to follow up.

Since this is a product/technical showcase, it would be great to slightly reframe the content so the focus stays on the technical capabilities, functionality, & usage examples rather than promotional messaging. This will help highlight the product details while keeping the entry informative, developer-focused, and aligned with the showcase format!

thank youuu!

[TKCollective]

Done — pricing references removed from the manifest, SKILL.md, the skill's example prompt, and README; kept a single "Learn more" link at the README's end. Showcase is now fully technical. Thanks for the clear guidance!