AI

ProofStamp for AI · Experiment paused

We’re rethinking how to make AI conversations verifiable.

ProofStamp AI is temporarily paused. Practical chat use created too much capture overhead and depended too heavily on whatever conversation history the AI host exposes.

Status: temporarily paused
Existing work stays public No active development Better capture path under exploration
ProofStamp AI experiment
What we tried
AI session Conversation and context exposed by the host
→
Portable record Saved artifact plus detached receipt
Session artifact *.proofstamp.json
Detached receipt *.proofstamp.receipt.json
What we tried

Capture. Save. Verify.

The experiment asked the AI environment to assemble the session evidence it could access, save it as a stable file, and verify the exact saved bytes.

1

Capture

Record only the conversation and context the current AI host actually exposes.

2

Save

Create a portable JSON artifact plus a detached receipt that can identify the exact file.

3

Verify

Read the saved bytes back and check the artifact against its SHA-256 receipt.

Why we paused it

Too much work inside the chat.

Capture overhead Practical chat use required too much work to assemble and preserve the available session evidence.
Host dependence The result depends on how much conversation history and file access the AI environment exposes.
Verification friction Reliable exact-byte verification requires stable file saving, readback, and SHA-256 support.
What comes next

Move capture out of the model.

Before resuming, we want to test a simpler approach: capture from host data or exports, then let ordinary software build and verify the record.

  • The AI should not need to reconstruct its own conversation.
  • Hashing, receipt creation, and verification should happen deterministically.
  • The workflow should be simple enough to use routinely.
  • The same proof boundary remains: file integrity does not prove truth, authorship, or provider authentication.

ProofStamp AI is paused.

The repository, prompts, and releases remain public as experimental reference while we explore a better capture path.

This pause reflects a usability finding from practical chat use, not a measured cross-platform performance or cost benchmark.