Full-thread upload workflow
Validate the export, confirm participants, and inspect the evidence-backed preview.
The quiet weeks count too. Grey Mirror follows repeated exchanges across your entire exported chat history, with dates and messages you can check. See what changed and what keeps coming back. Missing messages and life outside the chat still leave gaps.
By Layne Weant
Updated
Start with the most complete supported export you can safely provide, preserve sender order and available timestamps, confirm the participants, then compare similar periods and episodes. Grey Mirror measures observable changes in initiation, response timing, conflict escalation, repair, reciprocity, and future-planning language. Findings remain tied to evidence windows and confidence limits rather than becoming a verdict about either person.
Prepare the evidence
A long file is not automatically a complete or reliable relationship record. Inspect the export before upload so participant direction, order, timestamps, and coverage are strong enough for the question you want to ask.
What coverage unlocks
No universal message count or calendar threshold makes a finding reliable. Support depends on whether the relevant sequence repeats, the windows are comparable, participant mapping is sound, and the supplied history covers the question.
Measured pattern families
A responsible reading looks for convergence. A timing shift means more when initiation, repair, reciprocity, or follow-through changed in compatible ways; conflicting signals should narrow the interpretation.
Compare who starts distinct conversations, follows up, asks questions, and keeps shared topics moving.
Compare reply-gap distributions across relevant windows without treating one delay as intent.
Locate tension, acknowledgement, de-escalation, reconnection, and whether the issue returns.
Test whether similar conflict sequences repeat and how their aftermath changes.
Compare bids, questions, affection, plans, and repair responses instead of raw message counts alone.
Read parser quality, coverage, metric drivers, evidence references, and alternative explanations together.
Evidence standards
More messages do not automatically create stronger evidence. Confidence depends on parse quality, participant attribution, relevant coverage, comparable windows, supporting examples, and whether alternative explanations remain plausible.
Recurrence can show that a sequence appears repeatedly in the supplied thread; it still cannot establish private intent.
Even a complete export remains a record of that channel and period, not every event in the relationship.
Important findings should carry confidence and limitations so the support can be evaluated instead of assumed.
There is no universal message-count or time threshold. Use enough well-attributed, ordered history to include multiple comparable examples of the pattern you are testing. Sparse periods, missing channels, damaged timestamps, or a single episode should produce narrower claims and lower confidence.
Yes, when the archive uses a supported format and remains within the published upload limits. The workflow preserves order, validates the file, confirms participants when needed, and compares evidence windows. A longer file only helps when its coverage and structure are relevant and reliable.
The recurring ones: initiation and effort imbalance, response-timing drift, conflict escalation sequences, repair attempts and whether they were received, topic avoidance, affection drift, and whether future-planning language strengthened or thinned over time.
It can help test whether a recent observation differs from the earlier supplied record. Older messages provide a comparison baseline when their participants, timestamps, and coverage are reliable. They do not explain why a change happened or prove what will happen next.
Read the layers
Visual guide updated
Check the date range, participants and missing material in the supplied export.
Compare recurring initiation, conflict, repair and planning sequences within that coverage.
Look for sustained shifts against the conversation’s own earlier pattern, with surrounding context.
A larger history can improve context without proving intent. Start with one relationship question and inspect the windows that actually bear on it.