An open, local-first verifier for human and machine evidence.
No accounts. No uploads. No backend. Independently inspect signed human-presentation records, machine qualification evidence, and consequence-control projections while keeping unverified boundaries explicit.
↧
Drop a receipt, qualification bundle, or consequence-control projection
Signed receipt JSON or JWT · Machine qualification bundle JSON · Consequence-control projection JSON
Local-only verification. This page does not upload files or call a backend.
Recomputes the evidence locally, verifies the trust relationships, and generates a reviewer-ready report.
⌁ Local only✓ Signature checks□ Human + machine evidence▣ Foundation packet
Initial implementation stewarded by Aurifex Inc.
Verification verdict
—
—
—Local onlyNo upload
Signed consequence-control projection
Consequence Control
Integrity checked locally
Checks a signed verifier-side projection of machine admission, exact-action coherence, one-time consumption, provider evidence, outcome state, and the exact attached SYNC receipt bytes. It is not a canonical source-system state object.
Projection decision—
—
Admission—
Whether the exact action was admitted or refused.
Consumption—
Single-use reservation and consumption state.
Outcome—
Projection summary vocabulary. Canonical provider outcome and observed-effect relation remain separate in the consequence-control system.
Exact action CAID—
The CAID digest must equal the separately carried action digest.
SYNC receipt-byte reference—
The referenced SYNC receipt bytes are independently rehashed. MATCH proves which exact receipt bytes the projection references; it does not establish that the receipt carries or displayed the same typed action.
Human ↔ machine action bindingNOT ASSESSED
This sample does not prove that the attached SYNC receipt carries or rendered the same typed CAID/action.
Signer—
ES256 signature checked against a verifier-configured fixture pin. A self-disclosed key is not trusted by itself, and this is not a production signer or authority claim.
Protocol boundaries preservedMissing or conflicting outcome evidence remains unresolved with no blind retry. Production signer policy, canonical source-system state, durable server-side consumption, provider/effect reconciliation, deterministic display binding, and receipt-to-action equality remain separate.
Projection bindings
Machine qualification profile
Machine Qualification
Verified locally
Browser-local verification of the measured candidate, evaluation campaign, qualification statement, and current status under the supplied relying-party context. This result never authorizes or executes an action.
Qualification decision—
—
Cryptographic verification—
Native DSSE signatures verified under supplied trust pins.
Relying-party acceptance—
Accepted keys and thresholds come from the supplied relying-party context. This file does not establish that context's provenance.
Runtime candidate—
Measured runtime compared with the pinned candidate manifest.
Assignment scope—
Qualification is bound to the expected assignment and protected request.
Status currentness—
Status head and observation freshness checked locally.
Campaign graph—
Campaign lineage, terminal outcomes, and qualification graph checked.
Execution boundary preservedAuthorization composition, reservation, consumption, invocation, retry, and reconciliation remain with the consequence-control system.
Qualification bindings
Human-presentation evidence record
Receipt Summary
This section verifies what the receipt records as presented for human review. It does not independently observe the screen or verify a deterministic renderer or display attestation.
Intent statement—
—
Named identity—
Shown only if disclosed inside the receipt.
Signing authority—
Public verifier identity / issuer key.
Foundry origin—
Offline registry check for official SYNC signer attribution or browser-local relying-party acceptance.
Sealed at—
Time claimed by the receipt.
Authorization claim—
Authorization metadata claimed by the receipt; not independently observed by this verifier.
Display bindingNot assessed
No deterministic rendering or display attestation is verified in this build.
Receipt ID—
Portable record identifier.
Policy context—
Context labels, not legal certification.
Evidence—
—
Evidence foundation
Authentication Packet
Generated for evidentiary review: this does not determine admissibility, but it summarizes the receipt process, digital identifiers, verification checks, and limits for qualified review.
Not legal advice. Court admissibility still depends on the forum, relevance, objections, witness/certification foundation, and applicable rules.
Legal posture
Reviewer Matrix
A structured posture map for authentication, electronic process, digital identification, e-signature, and AI governance review. This is support, not a legal conclusion.
Verification detail
Verification Report
Tap to expand
Technical reference
Raw Technical Report
Tap to expand
Verification output
Sample verification report
Verified locally
SignatureValid
Cryptographic check completed in browser.
IntentMatched
Visible intent digest matches the receipt.
EvidenceHash matched
Evidence manifest is shown without upload.
Receipt chainMetadata present
Index and hash references are shown; continuity requires neighboring records or a trusted anchor.
ProfileSYNC Receipt v1.1
Required fields and supported export format recognized.
Machine qualificationSeparate local mode
Verifies machine-qualification evidence without granting execution authority.
Demonstration preview. Actual results are generated only after a receipt is selected.
Verification scopeTap to expandDesigned for evidentiary reviewTap to expand
Legal effect depends on facts, jurisdiction, implementation, and process controls.