What a report fingerprint verifies—and what it cannot prove
A fingerprint can help answer whether a report identity still matches the selected record fingerprints and report metadata tied to it. That technical check is not a judgment about the underlying events.
A matching Notarus report fingerprint can support one narrow integrity conclusion: the selected record fingerprints and report metadata match the report identity Notarus recorded. It cannot establish that statements are true, identify who authored or supplied every underlying item, prove the selection is complete, decide whether a person is credible, or determine whether the report is admissible.
1. Start with two different questions
An integrity question asks whether the content tied to a fingerprint still produces the same fingerprint. A truth question asks whether the people, events, and statements described in the record are accurate. A fingerprint comparison addresses the first question only.
Keeping those questions separate prevents a technical match from being described as proof of a larger factual or legal conclusion.
- Integrity: does the selected report identity still match?
- Meaning: what records and metadata were included in that identity?
- Truth and weight: what independent review is still required?
2. What Notarus includes in the report fingerprint
Notarus calculates a SHA-256 fingerprint from a canonical report identity: the preparer, reporting range, record order, generation time, record count, and the ordered fingerprints of the selected records. A production verification record stores the report fingerprint with limited report metadata so the QR path can compare the presented identity with that record.
This is a fingerprint of the selected records and report metadata, not a finding about why an event occurred. It should not be described as notarization, independent authentication, or a guarantee that the source material is complete.
A different selection, order, generation time, or record fingerprint produces a different report identity.
3. What a matching fingerprint can support
A match can support the conclusion that the report identity being checked corresponds to the selected record fingerprints and metadata recorded for that report. It gives a reviewer a repeatable integrity check instead of asking the reviewer to rely on the appearance of the document alone.
The reviewer should still inspect the report’s date range, selected categories, source labels, attachments, warnings, gaps, and visible corrections. The fingerprint does not make those scope decisions disappear.
- The report identity matches the recorded fingerprint
- The ordered record fingerprints and report metadata are bound to that identity
- A mismatch signals that the checked identity is not the recorded match
4. What a matching fingerprint cannot prove
A matching fingerprint cannot establish whether an underlying statement is true, whether a person is credible, who authored or supplied every underlying item, or whether important material was left out of the selected window.
It also cannot determine lawful collection, relevance, evidentiary weight, admissibility, clinical meaning, or the outcome a professional should reach. Those are separate questions that require source review, context, and the appropriate professional judgment.
- Truth or accuracy of the underlying statements
- Credibility, identity, or authorship
- Completeness of the source set or selected report
- Legal sufficiency, admissibility, or professional conclusions
5. Synthetic example: a match with narrow meaning
Imagine a demonstration report containing fictional exchanges, messages, and attachments. Its QR page says the demonstration fingerprint matches. That result means the synthetic report identity matches the fixed demonstration fingerprint used for the sample.
It does not mean the fictional events occurred, the fictional statements are credible, the sample includes every possible record, or a court would admit it. The public Notarus sample is intentionally separate from production report attestations.
The synthetic sample matches its demonstration-only report fingerprint. Review the included scope and limitations separately; the match makes no claim that the fictional events are true.
6. How a careful reviewer should use the check
Open the QR destination directly on the Notarus domain, compare the displayed report identifier and fingerprint status, and then read the report’s scope. Trace important claims back to the identified source material and note any warnings, gaps, or corrections.
If the report will inform a legal, clinical, employment, or program decision, the receiving professional should apply the independent review and evidentiary standards required for that decision.
- Verify the Notarus domain and report identifier
- Read the date range, filters, and included record count
- Inspect source context, attachments, gaps, and corrections
- Ask what was excluded and what still needs independent confirmation
Inspect the related product context.
Neutral custody exchange note
A calm, repeatable worksheet for recording one custody handoff with dates, direct observations, exact words, sources, and visible corrections.
Sources and further reading
These primary resources support the general boundaries and terminology in this guide. They do not turn the article into individualized legal, medical, or treatment advice.
More co-parenting record guides
Keeping a factual co-parenting timeline
A calm framework for dates, direct observations, exact words, attachments, and visible corrections.
8 min readOrganizing records for an attorney
Organize co-parenting records into a focused chronology with relevant dates, source attachments, visible corrections, and a clear index.
6 min readAdding a dated correction
A transparent method for adding a dated correction while leaving the earlier timeline entry untouched.