Deterministic evidence, measured in public
WardTrace

Anatomy of a Claim Passport

Every investigated claim produces one bundle: six entries, each hashed into the next. It is the product. Everything else exists to fill it honestly.

The six chained entries

  1. 1. Claim

    The claim under examination, exactly as billed: codes, dates, amounts, provider. This is the subject of the certificate.

  2. 2. Findings

    Each typed contradiction, one by one. Every finding names the rule that fired and the records that disagree, so a reviewer can open them and check.

  3. 3. Methodology

    The rules version, the code commit, and the validation status, including the honest line that error rates on real data are pending a pilot.

  4. 4. Gap list

    What this bundle does not verify: medical necessity and the clinical accuracy of readings. Stated inside the artifact, not in a footnote somewhere else.

  5. 5. Reproducibility kit

    Everything an opposing expert needs to re-run the checks byte for byte: dataset hash, rule identifiers, versions. Same inputs, same output, or the certificate fails.

  6. 6. Anchor

    Public timestamps proving the bundle existed, unaltered, at a point in time. Dual anchors: OpenTimestamps plus an RFC-3161 timestamp authority token.

Change one byte and the chain breaks

Each entry's hash is computed over its content plus the hash of the entry before it. That is the whole trick, and it is enough. Edit a date in the findings, round an amount, delete a gap-list line: the hash of that entry changes, so every hash after it changes, and the chain no longer matches its anchored fingerprint. Tampering does not need to be caught by a person. It is arithmetic.

The same property protects our customers from us. We cannot quietly revise a bundle after the fact either. Once anchored, the bundle is what it is.

Anchor states, in plain English

A bundle always tells you exactly how strong its timestamp currently is. There are four states, and we never present one as another:

Anchor state glossary
State What it means
MOCK A stand-in anchor for demos and tests. It proves nothing. We label it so you never mistake it for a real timestamp.
OTS_PENDING The bundle hash has been submitted to OpenTimestamps and is waiting for confirmation on the Bitcoin blockchain. Real submission, not yet provable.
OTS_CONFIRMED The OpenTimestamps proof is confirmed. Anyone can verify, independently and for free, that this exact bundle existed at that time.
TSA_CONFIRMED A timestamp authority has issued an RFC-3161 token for the same bundle. A second, independent public clock agrees.

Only the hash is ever anchored. Nothing about a patient leaves the machine.

See a bundle assembled