Trust & verification
Every score carries its own proof.
ValuuCompass scores are built to be checked: fingerprinted sources, a versioned method, deterministic scoring, and sealed snapshots anchored to Bitcoin. This page explains the chain, and how clients verify it, with or without us.
The chain of custody
Fingerprint. Seal. Anchor.
Three steps stand between a disclosure we receive and a score you rely on. Each one leaves a record that can be checked later.01
FingerprintEvery source document is SHA-256 hashed as we receive it and preserved in a content-addressed archive, together with the extraction artifacts derived from it. If a single byte of evidence later changes, the fingerprint stops matching.02
SealAll scoring records for a company are combined into one sealed fingerprint (a Merkle tree), with each indicator as its own entry. Any single score can be proven part of the sealed set without exposing the rest.03
AnchorOpenTimestamps anchors each sealed fingerprint to the Bitcoin blockchain. No company data goes on-chain, only a blinded cryptographic commitment. The public chain fixes what existed, and when.What the seal covers
The data, the method, and every version in between
A seal that only covered the numbers would prove very little. Ours binds the evidence, the exact method that scored it, and the full history of changes.Score attestation
SealedCompany—
Reporting year—
Snapshot—
Method version—
Indicator leaves—
Seal fingerprint · SHA-256…
Anchored to Bitcoin via OpenTimestamps · Block —
The attestation seal that travels with every scored snapshot.
The datasetEvery filing, page image, and extracted figure is fingerprinted the moment it enters the system. The seal binds the scores to the exact evidence they were computed from.
The methodFramework, prompts, and validators are hashed into one method version, sealed inside every snapshot. Every score can name the method that produced it.
The version historySnapshots are append-only. Nothing is edited in place: a correction becomes a new sealed snapshot beside the old one, so you can always show what was known, and when.
AI, constrained
Where AI works, and where it never does
AI is not used here the way a person uses a chatbot: feed a document, ask a question, trust the answer. It performs structured extraction under a fixed, versioned methodology. Code does the scoring.What the AI does
Reads filings at scale and returns structured evidence under fixed, versioned prompts
Drafts the explanatory text that accompanies scores, grounded in that evidence
Works inside one sealed, versioned method, identical for every company it reads
What the AI never does
Assigns a score. Every score is computed by deterministic code from the extracted evidence.
Answers open questions. Extraction runs against a fixed schema, not a conversation.
Changes silently. Any change to the method is a new method version, visible in every seal.
How clients verify
Four ways to check us, one of them fully independent
Verification is a client workflow, not a marketing claim. Inside the platform every score exposes its seal; the final step runs on the public Bitcoin chain, outside our systems entirely.Open the sealIn the platform, every score carries its attestation seal: company, reporting year, snapshot, method version, seal fingerprint, and Bitcoin anchor.
Recompute the verificationClients can re-run verification in the platform: the sealed records are re-hashed and checked against the seal fingerprint, so tampering has nowhere to hide.
Prove a single indicatorPer-indicator proofs show that a single score belongs to the sealed snapshot, without revealing anything else in it.
Check the chain yourselfDownload the standard .ots receipt and verify the anchor against the public Bitcoin chain with the open-source OpenTimestamps client, independently of ValuuCompass.
Anchors are aggregated by OpenTimestamps, an open standard. Receipts are standard .ots files any compatible client can verify.