HubPublic

Tamper-evident records for submitted AI answers

Re-verify a disputed AI answer with the evidence recorded at the time.

rawctx groups answer records, model-run information, source references, and correction history into one evidence record, then reconciles it with an independent system of record to detect missing or late records.

rawctx verifies the integrity of submitted records and reconciliation results. It does not by itself guarantee answer accuracy, actual delivery, or that a source was used in reasoning.

Reconciliation guide

SHA-256 hashes are sent instead of the original text. Do not enter personal data, secrets, or predictable sensitive phrases into an anonymous public receipt. Use the tenant HMAC path in production.

This anonymous receipt is public. Anyone with the link can view it. This form does not promise a retention period.

No signup · Hash-only submission · Public link

Independent Reconciliation

Find missing, unexpected, and late answer records first.

Compare rawctx records with an independent reference source before relying on cryptographic proof. A separate business system makes coverage gaps and timing differences visible.

Reconcile against a separate system of record.

Compare answer records with an independently sourced manifest to detect missing, unexpected, and late entries.

  • missing
  • unexpected
  • late

Keep the submitted record and its changes together.

Group the answer record, model-run information, source references, and correction history for export and review.

  • pip install rawctx
  • rawctx login
  • receipt URL

Verify submitted records without overstating them.

Integrity checks and explicit proof states cover the submitted record. They do not prove answer accuracy, actual delivery, or source use in reasoning.

  • Merkle proof
  • explicit proof states
  • documented limits

The same receipt shape in three lines.

After the browser receipt, create a workspace, get a token, and submit answer records with the same hash-first shape.

Build a Python logging call.

Start with the required parameters, then add any optional parameters you need.

Answer input
application_keydecision_idquestion_textanswer_text
Optional parameters
Proof verifier inputPaste into the verifier above
{}

Use public contracts and explicit states as the trust basis.

Review the public verifier contract, proof-state semantics, first-party platform monitoring, and documented limits before relying on a record.

  • Public verifier specification
  • Explicit proof states
  • First-party platform status
  • Documented trust boundaries
Verifier specificationOpen the public contract

Proof bundle verifier

Paste a rawctx proof bundle. The verifier checks its hashes, Merkle inclusion, signatures, and public witness bindings.

Public Merkle verifier spec