Seal a file
Files · messages · source checks

ProofBundle

Files, cryptographic receipts, and verifiable history

Local workbench
Application file: Loading actual application path…

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.

NameKindBytesModifiedActual pathFiles window
Custody storage loading.
0active artifacts
0agent records retained
0native RLM captures
0custody events
0algorithm source records
0captured vector cases

Signing scope loading.

Algorithm registration, captured vectors, executable providers, and observed test results remain separate states.

Capture coverage loading.

Implementation execution loading.
Archive execution evidence loading.

Custody and source records

No captured 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.

Sealed archives include artifacts and bytes, native state, agent observations, bridge actions, RLM captures, and retained history. Private signing keys and authentication tokens are outside automatic custody.

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.

⬇
Drop files here to seal
or click to choose files — processed on your device
Each seal enters History with its digest, signature, public key, and verification trace.
LOCAL WORKSPACE

File browser

Open a folder and choose files to load into the batch seal editor. The original files stay in place.

No folder selected

Choose a folder to access its files locally.

IDENTITY & CUSTODY

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.

Advanced: create a browser-held agent key

This creates a separate signing key inside this browser under the ID entered below. Native agents receive their own keys through the bridge CLI at spawn.

The private key stays in this browser. The exported record contains the public identity, AI-BOM, and state packet.

LOCAL ENCRYPTION

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.

SOURCE, TESTS & PROOFS

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.

Dual-signature seal
Seals the bundle above with two independent signatures — an ECDSA-P384 primary and an Ed25519 witness — both over one SHA3-384 digest of the canonical bundle. On verify: both valid → VERIFIED · exactly one valid → INDETERMINATE (needs investigation) · both invalid → INVALID_SIGNATURE. The witness key is bound in the signed content, so removing the witness gives INSUFFICIENT_SIGNATURES and replacing it UNEXPECTED_SIGNER.

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.

⬇
Drop a receipt file here to verify
or click to choose — a .pb.json file, or paste it below
Paste or edit the receipt (technical)
Trusted producers (0) — whose seals this browser accepts by name

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.

loading registry

Test Suite

The 1.0.0 conformance definition: every digest × every signature scheme this client runs, with one case built for each verdict the pair can reach, plus every profile, every envelope form and the boundary connectives. Each case's expected verdict is fixed by how it was built. Run it here and the verifier in this browser computes every result.

Advanced — coverage matrix, every case, downloads, imports

EU AI Act mapping, compliance evidence, and certification status

Law version: The ten-dimensional Article 10 model and its signed certificate record below preserve the original 2024 Official Journal profile. Regulation (EU) 2026/1744 replaced Article 10(1), deleted Article 10(5), and moved special-category bias-detection conditions to Article 4a. A result from the preserved 2024 model is not a current-law conformity decision. The source-bound issuer checker below is a separate profile.

Check an issuer certificate against the exact subject, criteria, and test-result files it names. Supply the issuer's public key from a source outside the certificate. This check verifies source bindings, the issuer signature, and the stated calculation; issuer authority and underlying measurements need separate evidence.

Check a source-bound issuer certificate

No certificate or outside issuer key has been checked.

Versioned requirement → source → evidence → verifier map

This is a source-linked index, not a conformity decision. It keeps the archived directive's 16 control groups, the 27 versioned legal atoms, the ten selected historical score axes, and the eight Vol. IV satisfier assertions distinct. No system-specific applicability, bound evidence, or verifier receipt has been supplied for these rows.

Checking embedded map bytes…
Original 2024 Article 10 mapping and amended application dates

Clause labels checked against the original Official Journal text of Regulation (EU) 2024/1689 (locally retained PDF SHA-256 bba630444b3278e881066774002a1d7824308934f49ccfa203e65be43692f55e). Current consolidated text and case-specific applicability require separate checking. Article 10(2)'s general governance requirement is not a separate vector dimension here.

Original 2024 Article 10 mathematical mapping and signed model record

This preserved model evaluates the entered requirement scores, lineage score, and ancestry tier. Its signed certificate record binds those inputs and the calculated result; it does not establish source measurements, current-law compliance, or independent issuer authority. The source-bound issuer check above addresses a separate certificate profile.





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.

Drop files here — or tap to pick
any type · any count · hashed locally, chunk by chunk


Artifact Library

Files added here stay in this browser's local library. Each imported file is hashed and kept with its bytes and catalog details. Use Seal to make a receipt, Verify to check one, and Agent chat to read bridge messages.

Add artifacts to the built-in library
Files are hashed with the ProofBundle engine and stored locally with their bytes, metadata, and content address.
0artifacts
0 Bstored bytes
0with custody commitment
0media types

History

This browser's seal and check actions are kept in an ordered local chain. Its links can reveal changes to retained entries; local timestamps and this chain alone do not prove an external time or an author's identity.

Optional: sync this browser history to your own server

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.

connecting

PROOFBUNDLE / TOGETHER

Conversations

Connecting participants…
Connecting…
Connecting…Enter to send · Shift+Enter for a new line
Signed bridge records appear here; registration or an ACK does not prove a live model reply.

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.

Agents0
No live state
Live chatter + actions—
Waiting for the bridge endpoint
Code + proof custody—
0PROVER REPOSITORIES
0LAST CYCLE CHECKED
0MERKLE SEGMENTS
0OTS RECEIPTS
Code activity appears here
Verifier endpoint
not checked
health
?
entries
?
tip seq
?
tip hash
?
Initiator
not set
→
Verifier relay
not checked
→
Recipient
not set
Actions
Recent lineage
not loaded
Action log
Bridge console ready.

Multi-agent orchestration

Reads a bounded, verified-room view from the local ProofBundle web bridge. Each message links to its exact source record, sequence, reply target, and available receipt. The bridge reports chain status; the browser does not independently verify the full chain. Registered identity does not imply an agent is online. The command composer below targets the separate local pb-lane-bus and never sends from this page.

Encryption layers — what is actually active
ProofBundle verified room (this panel's data)
Paged signed-record derivatives from the local web bridge. Open each source record to inspect its envelope and receipt.
Identity and transport scope
The local web bridge serves signed-room records. The separate pb-lane-bus command is a plaintext, hash-chained lane transport; it does not issue signed-room receipts.
Optional legacy HTTP lineage
When a reachable endpoint is configured, this panel can request ProofBundleBridgeEvent/v2 telemetry, unsigned at the source. The local folder ledger uses a separate transport and does not require this endpoint.
Algorithm registry
Full digest/MAC/KDF/signature/KEM/AEAD registry lives on the Algorithms tab — not duplicated here.
registered identities
?
loaded room records
?
room tip seq
?
filtered on
all lanes
Participants in loaded room 0
Feed 0
Local lane-bus command copy to your shell — nothing here executes

Use registered pb-lane-bus lane names here; signed-room agent IDs above are a separate registry.

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.

Overall status
When several claims are made about the same bundle, the overall status is the weakest one — a set of claims is only as strong as its least-supported member. Claim strength runs from excluded (rejected) up to released (fully supported).
No claims yet
Create a claim to start tracking assertions against 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.

No predictions yet
Register a falsifiable prediction to start tracking outcomes

Live Showcase Demos

6 end-to-end demos. Each generates a fresh key pair, seals real 1.0.0 bundles with the client's own sealing, and verifies them in several contexts and after several attacks, with the verifier's full trace. All crypto runs in this browser.

Live demos — ephemeral keys
Each "Run Demo" generates a fresh key pair. Results are deterministic in structure (same outcome tokens per context) but non-deterministic in key material. Every verdict shown is computed by the verifier when the demo runs; a demo prints its expected verdict beside the result only when the two differ. Verdicts these demos reach: VERIFIED, DIGEST_MISMATCH, INVALID_SIGNATURE, POLICY_DENIED, SIDE_INFORMATION_MISSING, RESOURCE_EXHAUSTED, LINEAGE_MISSING, LINEAGE_INVALID.