tate@programs ~/services/outside-proof-packet public evidence / replay commands / patch order

fixed-scope public proof / 3 business days

A $750 outside proof packet for launches buyers need to trust.

For agent-commerce, x402, MCP, UCP, marketplace, and security-tool teams that need a clean external readback before prospects, partners, reviewers, or analysts inspect the surface.

send surface sample format public proof

price: $750
surface: one launch
delivery: 3 days

proof.packet

$ prove launch --public-surface
inputs:
  one URL or repo
  approved public scope
  claim to support

checks:
  discovery files
  payment or tool boundary
  browser/readback behavior
  cache and CORS posture
  failure and retry evidence

output:
  evidence table
  replay commands
  ranked patch order

What it buys

One clear answer to: can an outside buyer verify this launch?

The packet is intentionally narrow. It creates buyer-readable evidence without touching private systems or pretending a broad audit happened.

Discovery readback

Public files and routes such as llms.txt, agents.md, MCP pointers, UCP profiles, manifests, sitemaps, and launch pages.

Boundary evidence

What is public, paid, free, gated, browser-readable, cache-safe, signed, replayable, undocumented, or blocked by validation before payment.

Patch order

A short remediation list ordered by launch risk, with exact commands that reproduce the findings from public surfaces only.

Fit

Use this when the surface is public enough to verify, but important enough to prove.

request packet

commerce

Agentic commerce and UCP

Catalogs, product feeds, checkout handoffs, Universal Cart readiness, merchant policy pages, partner demos, and AI-shopping launch claims.

x402

Paid APIs and payment gates

402 challenges, x402 v2 browser preflight, resource binding, no-store cache posture, receipts, retry behavior, and spend-map language.

mcp

MCP and tool launches

MCP server cards, well-known discovery, tool schemas, install docs, public demos, registry claims, support boundaries, and audit language.

security

Agent security products

Runtime security, tool authorization, policy actions, prompt-injection exposure, public docs, evidence packs, and buyer-facing control claims.

Scope boundary

Private-first where it matters. Public-only by default.

No login, no private endpoint guessing, no customer system probing, no wallet signatures, no real paid calls, no disclosure without sign-off. If the useful work needs private access or implementation, it becomes a separately approved sprint.

send

What to send

One URL or repo, the claim that needs proof, the approved public scope, and the deadline.

receive

What comes back

A private evidence table, command transcript, launch-risk patch order, and short buyer-safe summary.

upgrade

When it expands

If fixes are needed, implementation help starts at $2,500 and stays scoped to an approved patch list.

Ready

Send one launch surface.

The fastest useful intake is a URL plus the claim that has to survive outside scrutiny.

send surface