DEV Community

ProofPack
ProofPack

Posted on

ProofPack: hash-locked delivery receipts for AI client work

The problem

Agencies and freelancers increasingly ship AI-assisted work. The deliverable is often a prompt, a model output, and some surrounding context — but the handoff lives in email, Slack, or a shared doc. When a client asks “what exactly did we get?” you’re reconstructing history from chat logs.

That’s an operational problem, not a cryptography problem. Still, a simple cryptographic receipt helps: lock the bytes, stamp the time, share one artifact.

What ProofPack does

ProofPack turns that bundle into a timestamped, hash-locked delivery receipt:

  1. Paste the prompt, output, and optional context.
  2. The system computes a SHA-256 hash over the content and records a timestamp.
  3. You get a share link and a PDF — something you can send with the deliverable or file in the project.

Think packing slip, not notarization.

How the receipt idea works (high level)

  • Immutability via hash: Change a character in the prompt or output and the SHA-256 changes. The receipt points at a specific snapshot.
  • Timestamp: When the receipt was created — useful for “we locked this version on this date,” not for claiming legal finality.
  • Share link + PDF: Human-readable handoff for clients who won’t open a hex digest.

No special magic beyond hashing and packaging. The value is the workflow: one place to freeze “what we delivered” before the next revision cycle.

Who it’s for

Agencies and freelancers who want delivery transparency with clients — fewer ambiguous handoffs, clearer scope conversations after AI-assisted revisions.

Explicit disclaimer

ProofPack is a transparency / delivery-receipt tool. It is not legal advice. It is not a compliance certification. It is not court attestation. If you need legal or regulatory assurance, talk to a lawyer or auditor.

Soft launch / try it

MVP is live. Free tier: 3 receipts. Planned paid: Starter $39/mo, Pro $79/mo.
https://getproofpack.vercel.app

Feedback I’m hunting

  • Does “hash-locked receipt” communicate clearly to non-technical PMs and clients?
  • What fields belong in “context” for real agency workflows?
  • Any deal-breakers around pasting client prompts/outputs into a third-party tool?

Top comments (0)