A record you can inspect.
How a Proof Capsule relates a bounded request, compiled policy, allowed result, trace and budget change.
One record for one run
A Proof Capsule links a successful local run to its request ID, capability, policy version, allowed output and trace. Ordinary time labels use Eastern Time (America/New_York), with EST or EDT shown for the recorded instant. Its raw JSON and downloads retain ISO UTC timestamps. Its execution mode is local-sample.
The Console generates a new request ID and nonce for a new call. Replaying a completed record keeps its original identity, times, output and nonce.
Included fields
New records use protocol oclith/proof-capsule and schemaVersion 2.0.0. The record includes protocol, schemaVersion, serialization, algorithm, requestId, capabilityId, policyVersion, executionMode, intentDigest, policyDigest, outputDigest, traceDigest, receiptDigest, nonce, generatedAt, expiresAt, budgetBefore, budgetAfter and status.
The redacted intent includes the capability, requested return fields, expiry, input digest and input length. It does not include the submitted raw input. The policy is the compiled public sample Manifest. The trace describes the actual local processing stages and their result.
The Capsule's output contains the fields that passed the result boundary. A rejected call retains its failure reason and trace in the Console and does not receive a successful Capsule.
Serialization and SHA-256
New records use oclith-canonical-json-v2. The protocol, schema version and serialization identifier are covered by the receipt digest. Historical records with the tuple celino/proof-capsule, 1.0.0 and celino-canonical-json-v1 are verified using their original contract and hashes. Historical Celino Manifest declarations retain their original shape and digest; a schemaVersion is not inserted into old records. Object keys are sorted recursively, arrays preserve their supplied order, and only finite JSON values are accepted. Manifest normalization separately trims strings and deduplicates and sorts policy field lists.
Web Crypto computes SHA-256. If a secure digest implementation is unavailable, compilation reports a specific error. The interface never labels a substitute hash as SHA-256.
The policy digest excludes policyDigest itself. The intent, output and trace digests cover their corresponding record values. The receipt digest covers the Capsule contents without its own receiptDigest field.
The browser storage key, signed-session cookie and durable registry namespace retain their existing identifiers so saved work and owner sessions remain accessible after the brand update. This compatibility layer does not rename old files, regenerate record IDs or rewrite stored JSON.
Check the covered content
Use Verify in the Console to recalculate the Capsule's digests and compare them with the stored values. The result is Integrity matched when the covered content agrees. Editing a covered output, policy, trace or record field should make verification report a mismatch.
The Console also exposes the JSON for copying and downloading. These operations do not create another call or change the original execution record.
What integrity means
Integrity checking detects changes to the covered content relative to its digests. A person who changes both a record and all its hashes can create a different internally consistent document. Without an independently trusted signature or anchor, a digest is not proof of origin.
This Capsule does not prove that an unseen private source exists, that private execution was correct, or that a trusted enclave ran the work. It is not a zero knowledge proof, an on-chain settlement or a payment receipt.
Keep evidence bounded
Do not place original private material, sensitive input or internal policy prose into a shared call record. The sample's redaction avoids raw input export, but an output can still carry sensitive information if an owner declares an overly broad schema.
In a production deployment, define what each field reveals, who can inspect it, how long records persist and which external trust mechanism, if any, attests to the execution.