Trust should be inspectable
A promise can be revised. A public record lets families and professionals see what was reviewed, by whom, and when.
Health-adjacent technology often asks users to trust a chain of invisible work. Trust the sources. Trust the translation. Trust that the reviewer was qualified. Trust that the page has not changed since the review. Trust that a correction will be disclosed.
Many companies answer those questions with another promise. We think the better direction is inspection: give families and professionals enough information to test the parts of the claim that can be tested.
Provenance can show who signed what and when. It cannot prove that the judgment was correct.
Three layers that should not be confused
1. Scientific quality
This is the substance: whether the claim accurately reflects appropriate evidence, whether important limitations are visible, whether the practical action is proportionate to the evidence, and whether the boundaries between education and medical care are clear.
Scientific quality depends on judgment. No cryptographic system can decide whether a study was biased, whether a population is relevant, or whether a family-facing sentence creates false certainty.
2. Governance
Governance answers who was responsible for that judgment. Which advisory lane owned the content? Who was the reviewer of record? Were conflicts disclosed? Was another specialty consulted? Was the decision approval, conditional approval, revision, escalation, or hold?
A public roster without decisions is incomplete. A decision without an identifiable scope is easy to overextend. Governance connects people, authority, and accountability.
3. Provenance
Provenance answers whether the content now visible is the same content attached to the recorded decision. This is where cryptographic hashes and public timestamps can help.
A hash function converts a digital file or message into a fixed-length digest. Change even a small part of the input and the digest changes. The NIST Secure Hash Standard specifies algorithms including SHA-256 that can be used to detect whether a message has changed since a digest was generated.
A public consensus log can add an independently inspectable timestamp and ordering record. Resilient Kids’ Trust Ledger is designed to connect content versions and review events to those tamper-evident records. When a ledger entry is present, a reader can use it to test a narrow but valuable claim: does this version match the version recorded at that time?
What a ledger can prove
- that a particular digital record existed by a recorded time;
- that the current content matches, or does not match, the recorded version;
- that a stated review event is associated with a particular version, when the identity and signature system are in place;
- that later edits cannot be quietly presented as the unchanged original record.
What a ledger cannot prove
- that the cited research was high quality;
- that the reviewer made the right scientific judgment;
- that the reviewer was free from every source of bias;
- that a population-level recommendation is right for one child;
- that a company will respond well when new evidence appears.
Those limitations are not reasons to abandon provenance. They are reasons to describe it accurately. Cryptography is strongest when it is used for the questions it can answer rather than as a futuristic synonym for trust.
Identity matters too
A signature is only as meaningful as the identity and authority attached to it. For named scientific advisors, persistent identifiers such as ORCID can help connect a reviewer to a durable scholarly identity. A governance record should also show the person’s role, scope, affiliation, disclosures, and the specific work reviewed.
Resilient Kids currently has 31 mapped advisory lanes: 27 active and four bench. Internal Editorial Review is the reviewer of record across the active lanes today, while named external specialists are onboarded lane by lane. The bench lanes remain marked for assignment. Named external sign-offs should appear only when the person exists, the identity is verified, the scope is accepted, and the review has actually happened.
A simple inspection checklist
When a parenting or health platform makes a scientific trust claim, ask:
- Can I see the sources? Are limitations and uncertainty visible?
- Can I see the reviewer’s scope? Does the expertise fit this claim?
- Can I see the status? Is this internal review, named external review, or still awaiting assignment?
- Can I see the decision? What did review change or approve?
- Can I see the version and date? Has the content changed since review?
- Can I see corrections? Does the organization show meaningful updates rather than silently replacing them?
Trust is a system, not a badge
No ledger, roster, or evidence hierarchy deserves trust by itself. The useful system is layered: careful evidence translation, people accountable for bounded judgments, and records that make versions and decisions harder to rewrite after the fact.
The goal is not to ask readers to admire the machinery. It is to give a skeptical parent, clinician, researcher, or partner a fair chance to inspect the claim and reach their own conclusion.