Message-level evidence
Specific message references or excerpts when the report payload and access gating allow it.
If a report makes a strong claim, you should be able to check it. Grey Mirror pairs supported findings with counts, dates and message evidence. This page explains what we require and when the available history is too thin for a confident answer.
By Layne Weant
Updated
Evidence is any report support that connects a claim to the uploaded thread: message references, timeline windows, participant counts, metric deltas, parser diagnostics, and confidence labels. Evidence is not a mood, hunch, or unsupported summary.
Grey Mirror evidence can exist at multiple levels. The right level depends on access, privacy, and what the stored result payload actually contains.
Specific message references or excerpts when the report payload and access gating allow it.
A time range where a signal appears repeatedly, such as repair after conflict or a cooling response pattern.
Counts, deltas, confidence, and participant splits behind a score or tile.
Cross-metric agreement that explains the trajectory rather than a single isolated signal.
A responsible report should hold back when the evidence is not safe to show or not strong enough to support the claim.
Confidence labels should explain reliability, not decorate the UI. A high-confidence label needs enough data and supporting evidence; a low-confidence label should tell the user what is missing.
Evidence belongs inside gated report surfaces, not public pages. Public pages can explain evidence standards, but they should never expose a user upload, private report artifact, or full-only evidence link.
Grey Mirror's evidence approach aligns with established principles from digital forensics, legal evidence standards, and information quality frameworks.
These references inform our evidence standards but do not constitute legal advice. Grey Mirror is a pattern analysis tool, not a legal or clinical diagnostic.
Our evidence preservation follows principles from <a href="https://www.nist.gov/itl/sed/nist-special-publication-800-86" target="_blank" rel="noopener noreferrer">NIST SP 800-86: Guide to Integrating Forensic Techniques into Incident Response</a>, focusing on maintaining data integrity and traceability from export to analysis.
Our confidence bands and evidence thresholds draw from <a href="https://www.law.cornell.edu/rules/fre/rule_401" target="_blank" rel="noopener noreferrer">Federal Rules of Evidence Rule 401</a> (relevance) and <a href="https://www.law.cornell.edu/rules/fre/rule_402" target="_blank" rel="noopener noreferrer">Rule 402</a> (admissibility), adapted for pattern analysis rather than legal proceedings.
Our evidence quality checks align with information quality frameworks that emphasize accuracy, completeness, and traceability of data sources. We apply these principles to message exports and parser outputs.
It is a short explanation of which evidence and metric families drove a score, including confidence and evidence quality.
No. Public samples explain the format without exposing user uploads, private report artifacts, or account-scoped evidence identifiers.
No. Missing evidence means the report cannot support a conclusion.
Read the layers
Visual guide updated
Identify the supplied messages, sender mapping and date window supporting the observation.
Explain what was counted or compared, including the relevant denominator.
State confidence, limitations and plausible alternative context before drawing a conclusion.
If a report cannot show this trail, treat the claim cautiously. Specific wording does not compensate for missing evidence.