Evidence Bundles

Portable, auditor-grade artifacts generated from a Pact transaction.

Why Pact exists

Without Pact

  • Logs are informal and mutable
  • Payments prove nothing about intent
  • Failures are ambiguous
  • Disputes require humans and guesswork
  • Insurance and audit are impossible

With Pact

  • Negotiation is signed and hash-linked
  • Intent and policy are explicit
  • Settlement outcomes are deterministic
  • Failures are classified with blame
  • Evidence is portable and verifiable

Pact produces evidence for successful transactions, policy aborts, timeouts, and settlement failures. Failure is a first-class outcome.

Transcript replay (redacted)

Documentation-friendly render of transcript verification output.

Transcript replay screenshot

Open transcript replay SVG (If the image fails to render, this link should still work.)

What's inside

  • Signed transcript
  • Verification report (PASS/FAIL + reasons)
  • Settlement attempt records
  • Failure events (if any)
  • Judgment output (DBL)
  • Metadata (policy hash, version, timestamps)

Redacted evidence bundle

Public-safe example. All identifiers are redacted; structure is representative.

{
  "bundle_version": "pact-evidence/1.0",
  "transcript": { "schema": "pact-transcript/4.0", "rounds": 3, "final_hash": "0x8b2c…3c4d" },
  "verification": { "status": "PASS", "checks": ["signatures","hash_chain","policy_hash_match"] },
  "judgment": { "result": "NO_FAULT", "confidence": 1.0 }
}

Download: redacted_evidence_bundle.json

CLI output snippet with hashes

What an auditor or third party can independently reproduce.

$ pact replay --transcript ./.pact/transcripts/transcript-…json
[pact-replay] schema: pact-transcript/4.0
[pact-replay] integrity: VALID
[pact-replay] final_hash: 0x8b2c4d8a0f6e3a1c…a2b3c4d

$ pact bundle --transcript ./.pact/transcripts/transcript-…json --out ./public/redacted_evidence_bundle.json
[pact-bundle] policy_hash:        0x4f0a7c9d2e1b…234567
[pact-bundle] constitution_hash:  0x1c9f2d3b7a0e…7d6e5

Download: cli_output_with_hashes.txt

Admissible vs claimed evidence

Admissible: Hash-linked + signed + verifier-checkable. Evidence that can be cryptographically verified against the transcript and policy.

Claimed: Anything without transcript linkage (screenshots, logs, emails). These are assertions without cryptographic proof and are not admissible under Pact's rules of evidence.

Integrity + tamper detection

Any modification to a signed transcript breaks the hash chain and invalidates signatures. Evidence bundles include cryptographic proofs that enable independent verification of integrity.

Evidence references (hashes, signatures, policy matches) are trusted because they can be verified deterministically. Claims without corresponding evidence refs are not admissible.