Verify a third party from their public record alone

Public Signal Verification

A sealed verification record on any named subject — built from their public footprint without their participation. Regulatory listings, sanctions corpora, leak datasets, registry filings, on-chain activity, and adversarial-review patterns are reconciled into a single hash-anchored attestation under Policy v2.0. Replay-deterministic. Issued with a sealed certificate.

Open a verification →How it worksTry a sample subject
What it is

One product. Seven verification profiles. Any subject. Any jurisdiction.

Pick the profile that matches the question you're answering -- Sovereign Wealth, Defence Acquisition, Sanctions Enforcement, Climate, Domestic Grant Fraud, Fincrime Compliance, or UK Secured-Lending Compliance. Or run all seven in one sealed sweep with a fold-of-roots hash anchor.

Claim reconciliation
Every public claim made by or about the subject is extracted, indexed, and cross-checked against the connector corpora the platform is wired to.
Contradiction scan
Where two source corpora disagree, the contradiction is surfaced, scored, and recorded against the policy-sealed VRO.
Hash-anchored seal
The verification record is sealed under Policy v2.0 and Merkle-rooted. Replay produces the same hash. The seal is the verification.
Sovereign certificate
A signed certificate is issued at /attest/<vro_code> — the public-facing artefact that downstream parties can verify in one click.
How it works

Open the record. The pipeline does the rest.

STEP 01
Open the VRO
Subject name, jurisdiction, market code. Tier selected. The record opens in PENDING_EVIDENCE state under a fresh policy seal.
STEP 02
Pipeline executes
Data Lobby ingests public records. Bastion enclave runs the reconciliation. Forensic enclave scores contradictions. VRO enclave seals the result.
STEP 03
Seal anchors
The sealed VRO Merkle root is anchored to the epoch chain. The record is now replay-deterministic and externally verifiable.
STEP 04
Certificate issues
A signed certificate is issued at /attest/<vro_code>. Recipients verify in one click. Subject can dispute via the F46 channel.
Try it on a known subject

Six sample verifications

Run the engine on a pre-loaded subject. The sample runner is hosted in the partner-showcase environment so demo runs do not consume production capacity.

AI
Delve · YC compliance startup
Public claim verification on a compliance-tech founder narrative.
Run sample →
SANCTIONS
Synapse Financial
Banking-as-a-service collapse — claim-vs-reality reconstruction.
Run sample →
SANCTIONS
FTX
On-chain reconciliation against published audit narrative.
Run sample →
SANCTIONS
Wirecard
Multi-jurisdictional shell-network traversal.
Run sample →
SANCTIONS
Evolve Bank & Trust
Regulator-listing cross-reference.
Run sample →
HEALTH
Theranos
Capability-claim contradiction at scale.
Run sample →
Pricing

Three tiers. Same hash chain.

Every tier produces a sealed VRO under the same Policy v2.0 hash. Tier difference is depth, jurisdictional breadth, and forensic cross-reference count.

Standard
Public Signal Verification — Brief
$5,000
  • Single named subject
  • Claim register + contradiction scan
  • Sealed certificate at /attest
  • Hash-anchored derivation chain
  • Forensic-firm cross-reference
Open this tier →
Standard
Public Signal Verification — Brief Pro
$25,000
  • Cross-jurisdictional registry traversal
  • On-chain forensic deep dive
  • Five-firm forensic cross-reference
  • Three-week SLA
  • Sealed certificate
Open this tier →
Sovereign
Sovereign Intelligence Report
$75,000
  • F46 audit-trail seal on every read
  • Multi-jurisdiction sanctions cross-ref
  • Predictive next-vehicle section
  • Sealed certificate + Merkle root
  • Regulator-grade chain of custody
Open this tier →
Public-record doctrine

Public Signal Verification reads only from the subject's public record. The subject is not asked to participate. After issuance, the subject can request the verification record and lodge a dispute through the F46 channel. All processing is logged in the audit ledger; every read against a sealed record is itself sealed under F46.

Ready to verify a subject?

Open a Public Signal Verification →