ProofBundle
Files, cryptographic receipts, and verifiable history
Files · This computer
Live mounted drives and directories. Retained archive artifacts remain in the custody view below. Directory browsing records metadata; file bytes are captured through Capture artifacts.
| Name | Kind | Bytes | Modified | Actual path | Files window |
|---|
Signing scope loading.
Algorithm registration, captured vectors, executable providers, and observed test results remain separate states.
Capture coverage loading.
Custody and source records
Native record inspector
Original schemas, hashes, identities, source references, boundary results, and proof assumptions remain retained. Large records use bounded previews; complete originals remain in the archive. Observation and certification have separate evidence states.
Selection opens the record's source, identity, scope, and evidence state.
Bounded native record preview and hashes
No record selected.
RLM source capture
Read-only queries retain complete native result records, source identifiers, SQL, parameters, and result hashes. The existing memory databases and source files remain unchanged.
Source paths and established RLM scripts
Source metadata loading.
Provenance supplements
Origin records remain immutable. Later source, authority, consent, or context assertions become separately retained supplements. An assertion does not automatically grant authorization or a verified verdict.
Seal a file
Drop in a document, image, model, or dataset. ProofBundle gives it a cryptographic receipt you — or anyone — can check later. It never leaves your device.
File browser
Open a folder, inspect its contents, and bring selected files into custody.
No folder selected
Choose a folder to access its files locally.
Register an agent session
Create a distinct Ed25519 identity, signed AI-BOM, and state packet locally. Known model and provider fields can be supplied; unknown fields remain empty.
Keys stay in this browser. The exported record contains the public identity, AI-BOM, and state packet.
Signing identity
Your browser keeps a local Ed25519 key and signed identity record. The same identity signs custody events across reloads.
Local recorder
Loading identity…
The public export contains no private key. A recorder signature attributes this browser’s custody action; source authorship and operator endorsement are separate.
Encrypt a file
Encrypt for a recipient with ML-KEM and authenticated encryption. The downloaded receipt binds the encrypted bytes to your signing identity.
Files and keys are processed locally. Keep the recipient’s decryption key to reopen the file.
Implementation and scope
This file workflow uses a single authenticated envelope and reads the selected file into memory. Large streaming archives use the separate PB-VAULT-1 implementation. JavaScript timing resistance and implementation-refinement proofs remain explicit obligations in the cryptographic evidence ledger.
Cryptographic basis
Inspect each implementation, its normative source, measured evidence, and remaining proof obligations.
855 NIST published sample cases pass. This is sample-vector conformance, not CAVP validation or FIPS module certification.
Eight abstract Lean interface/model theorems were audited without axiom dependencies. JavaScript implementation refinement and timing resistance remain open.
Seal a ProofBundle
Build and cryptographically sign a new bundle — any registry digest × any registry signature scheme, classical or post-quantum — with Merkle root commitment. Your private key never leaves the browser.
Verify a receipt
Drop the receipt file you got when something was sealed. You'll get a plain pass/fail — the sealed data never leaves your device.
Paste or edit the receipt (technical)
Advanced options — lineage, context, timing
Algorithm Registry
The authoritative registry is loaded from ALGORITHM_REGISTRY.json. It separates recognition, implementation, and browser execution so an algorithm is never presented as operational merely because its name is known.
Test Suite
1,097 recorded test cases, each with a known correct result, used to confirm this engine behaves correctly. Run them below to see the results computed fresh, right now, in your browser.
Advanced — full vector ledger, coverage matrix, custom imports
Formal Compliance Certification
Evaluate the applicable requirement profile, compliance vector, threshold vector, gate, and score; bind the result to the artifact, AI-BOM, registry state, issuer key, timestamp, and lineage; then issue a portable cryptographically signed certification.
Files — Universal Artifact Custody
Seal any file type — binaries, PDFs, models, tarballs, images. Files are read in chunks and committed under a Merkle root (RFC 6962 style, same domain separation as the bundle tree), so large artifacts hash in constant memory and any chunk can later carry a compact inclusion proof. Nothing leaves the browser.
Artifact Library
A durable, local-first catalog for source files, datasets, model artifacts, proof objects, receipts, and evidence. File bytes and metadata remain in this browser's IndexedDB unless explicitly exported.
History
Everything you've sealed or checked in this browser, kept in order. Each entry links to the one before it, so if anything in the history were altered, that would be detectable. You can export this history at any time as proof of what happened and when.
Everything above works fully offline with no configuration. Turning this on additionally mirrors your local ledger entries to a server you control — it never replaces local storage, and every seal/verify action still succeeds instantly even if the server is unreachable.
Open current-state proofs · protected machine ledgers remain local to the installation.
Conversations
Bridge console
Watch the local ProofBundle verifier relay, inspect the lineage, register explicit lane identities, seal messages, route envelopes, read inboxes, and verify the chain. This console does not claim inherited identity; it only reports what the verifier endpoint confirms.
Multi-agent orchestration
Reads pb-lane-bus directly — the same append-only, hash-chained,
local file transport every agent lane on this host writes to
(~/pb/live/bus/messages.ndjson, served same-origin at
agent/live-bus/). This is not the sealed-envelope agent mesh
(agent/envelope.mjs, X25519 + ChaCha20-Poly1305): that protocol
is real and implemented, but its only server is the local ProofBundle broker,
which the operator revoked on 2026-09-23 and which this page will not
restart. The panel below composes exact pb-lane-bus commands for
you to run in your own shell; it does not execute them from the browser.
prev_hash), plaintext body. Tamper-evident, not confidential, not signed.ProofBundleBridgeEvent/v2 telemetry, unsigned at the source. Different protocol from the sealed mesh above despite sharing a port.Deployment profiles
Ten pre-built rule sets for common cases — clinical AI, financial systems, high-risk deployments, and more. Pick one to see the exact checks it runs, then load it straight into Seal or Verify.
Claims Lifecycle
Manage verifiable claims against ProofBundles — from submission through evidence review to acceptance or rejection. Claims track the provenance of assertions made against sealed bundles.
Prediction Ledger
Register falsifiable predictions tied to ProofBundles. Confirm or falsify each prediction with an evidence note — falsified predictions create an audit trail in the verification chain.
Live Showcase Demos
5 end-to-end demos. Each generates a fresh ED25519 key pair, seals a bundle with Merkle root commitment, and verifies against multiple contexts — showing all major outcome tokens with a full execution trace. All crypto runs in-browser.