Communication taxonomy
A proprietary taxonomy spans communication acts, emotion, needs, boundaries, repair, risk, tactics and topics. Labels describe communication, not clinical diagnoses.
Grey Mirror has 30 analyzers built on up to 47 models. Full-history analysis compares both participants across communication patterns, with supporting messages and stated limitations.
By Layne Weant
Updated
Grey Mirror has 30 analyzers built on up to 47 models. Full-history analysis compares both participants across communication patterns, with supporting messages and stated limitations. The measurements below cover repair, reciprocity, effort, response timing, communication shifts and recurring patterns.
Grey Mirror has 30 analyzers built on up to 47 models. Full-history analysis compares both participants across communication patterns, with supporting messages and stated limitations. Which components run and which measurements appear depend on the export, enabled stages, model availability and report access. Not every component runs in every report.
The published model count combines 37 classifier roles, including rule-based analysis and 9 taxonomy heads, with 10 configured transformer checkpoints. It is a component inventory, not a count of independently trained models. The checkpoints include public models as well as Grey Mirror's own taxonomy backbone.
Grey Mirror measures communication signals, timing, change and recurrence across the full history, finds the messages that support each finding, and explains the results in plain English.
More components alone do not establish greater accuracy. Compare coverage, metric definitions, evidence links, evaluation results and the report itself.
A proprietary taxonomy spans communication acts, emotion, needs, boundaries, repair, risk, tactics and topics. Labels describe communication, not clinical diagnoses.
Grey Mirror links repeated episodes, recurring loops and changes across the timeline, so a pattern that returns months later is recognised as the same pattern.
The complete report brings together a cinematic explanation, timeline and participant comparisons, metric drivers, supporting evidence, confidence and limitations, plus available action-plan and conditional-forecast sections. Sparse or missing evidence can make a measure unavailable.
Metrics are not verdicts. They are structured signals that become more useful when they agree with each other across the timeline and less useful when the evidence is thin.
The public metric library defines what each metric means, what question it answers, how it is roughly measured, and what evidence context it needs.
A composite report-level read of stability, repair, reciprocity, timing, and risk signals when enough data exists.
Is the thread moving toward steadier connection or toward more strain?
Combines normalized metric families rather than treating one dramatic message as the whole answer.
Best read as a multi-signal score with supporting evidence windows and confidence labels.
Needs enough timeline coverage, both participant labels, and stable parsed timestamps.
How often conflict or tension is followed by useful de-escalation, accountability, or reconnection.
Do conflicts actually recover, or do they restart with the same unresolved pattern?
Looks for rupture windows, follow-up windows, apology or accountability language, and return-to-baseline signals.
Best with complete exchanges around disagreement and aftermath; offline repair lowers evidence density.
Best with complete exchanges around disagreement and aftermath.
The balance between moments that damage trust and moments that restore it.
Is the relationship absorbing stress or accumulating unresolved damage?
Contrasts tension markers, escalation, blame, invalidation, repair bids, and follow-through windows.
Best when rupture and repair both appear in the text record with clear before, during, and after context.
Needs enough before, during, and after context around conflict.
Reply latency patterns by participant, time period, and context.
Who tends to wait, who tends to chase, and whether the pace has shifted.
Uses timestamp gaps after normalization and excludes gaps that are not countable.
Best with reliable timestamps, intact sequence, and enough repeated windows to separate ordinary schedule from drift.
Requires reliable timestamps and correct participant mapping.
Whether reply patterns get faster, slower, more selective, or more asymmetric over time.
Did the relationship cool gradually, or did one person suddenly change cadence?
Compares timeline windows and participant-level latency distributions.
Best with long histories and consistent timestamp coverage so slower pacing can be compared across phases.
Best with long histories and consistent timestamp coverage.
How evenly the conversation passes between participants instead of collapsing into monologues or pursuit.
Does one person carry the thread, explain more, or repeatedly reopen the same issue alone?
Compares message runs, response density, unanswered streaks, and follow-up burden.
Best when topic type, response quality, and repeated back-and-forth are visible.
Needs accurate speaker attribution and enough back-and-forth.
Differences in initiation, follow-up, emotional labor, planning, and repair attempts.
Is the thread reciprocal, or is one person maintaining the relationship by default?
Combines initiation, unanswered bids, follow-through, planning, repair, and engagement markers.
Best when ordinary days, conflict days, planning days, and follow-through all appear in the upload.
Best when the uploaded history includes ordinary days, conflict days, and planning days.
Whether warmth, affirmation, humor, appreciation, and bids for connection are returned or ignored.
Does positive energy circulate, or does it mostly travel one way?
Counts and compares positive bids, reciprocal responses, and ignored warmth across windows.
Best with surrounding message context around affectionate, humorous, sarcastic, or supportive exchanges.
Needs message-level context around affectionate or supportive exchanges.
Signals of pressure, control, invalidation, apology avoidance, boundary testing, or one-sided decision control.
Does one person repeatedly shape the terms of the relationship while the other adapts?
Looks for repeated pressure patterns, dismissal, coercive wording, threats, blame loops, and boundary response.
Best with repeated pattern evidence, recurrence, intensity, and trust-page resources for safety-related concerns.
Requires repeated pattern evidence, not a single phrase.
How often concrete future plans appear, who initiates them, and whether they become action.
Is future talk specific and mutual, or vague and noncommittal?
Separates concrete logistics, time-bound plans, vague someday language, and follow-through.
Best with enough planning conversations, follow-through windows, and platform coverage to compare.
Needs timestamps and enough planning conversations to compare.
Changes in length, tone, response cadence, conflict style, affection, or planning across the timeline.
What changed, when did it change, and which signals changed together?
Compares windowed metric changes and participant-level trend direction.
Best with multiple months or distinct relationship phases so timeline shifts can be compared.
Best with multiple months or distinct relationship phases.
The direction of emotional movement across windows when sentiment, repair, warmth, and tension align.
Is the relationship gaining connection, flattening, or moving toward shutdown?
Uses multiple signal families together instead of one sentiment counter.
Best with enough messages per window and surrounding context for emotional language.
Needs enough messages per window for confidence.
Repeated relationship episodes that follow similar sequences, such as tension, apology, temporary warmth, and relapse.
Are you solving a problem or replaying the same episode with new words?
Compares episode structure, triggers, sequence order, and aftermath when sequence intelligence is available.
Best with repeated episodes that have clear starts, follow-up, and aftermath windows.
Needs repeated episodes with clear starts and aftermath windows.
A label that explains whether a metric is strongly supported, partially supported, or too thin to trust.
How much should the user rely on this particular claim?
Considers message count, window coverage, parser quality, participant confidence, and supporting evidence density.
Low confidence is not a negative finding; it means the evidence needs more support.
Uses parser diagnostics, timeline coverage, evidence references, and metric support.
Power dynamics, recurring loops, emotional momentum, and relationship-health style scores should be treated carefully because they combine multiple weaker signals into a stronger claim only when the evidence is dense.
The report should not dump a wall of analyzer names. It should translate the metric stack into a small number of useful reads: what is stable, what is drifting, what repeats, and which signals deserve caution.
A compact read of overall health, repair, affection, timing, and balance. It is useful for orientation, not final judgment.
Expandable metric families for users who want to inspect why a score moved instead of trusting a headline number.
Windows, counts, confidence, and report notes that explain where the metric came from and when confidence should be lower.
A useful metrics library should own the exact questions people ask before they upload: what is measured, how to read it, what can go wrong, and how the metric connects to the report.
No. Counts help, but Grey Mirror should also consider timing, sequence, participant role, surrounding messages, and confidence.
Because a trustworthy metric needs enough parseable messages, timeline coverage, and participant confidence to support the claim.
When later runs are linked to the same report lineage and contain comparable data, longitudinal surfaces can show change over time.
Reciprocity is measured as a set of paired ratios across the whole thread rather than a single number: who opens conversations, who sends the second message after a reply, who asks questions back, and who closes threads. Each ratio is compared against that pair’s own historical baseline, because a 60/40 split is normal for some couples and a sharp change for others. The direction and stability of the ratio over time matters more than its value in any single week.
Effort balance combines four counts per participant: conversation initiations, follow-up messages after no reply, questions asked, and concrete plans proposed. Message volume alone is a poor proxy, because one person can send many short reactive messages while the other does the structural work of starting and planning. Grey Mirror reports each component separately so a single lopsided component does not read as global imbalance.
Emotional reciprocity looks at what happens after one person raises something vulnerable. The measurable unit is the response to a disclosure: whether it was acknowledged, matched with a disclosure of similar depth, met with a follow-up question, deflected, or left unanswered. Tracking that response distribution over time shows whether emotional openness is met symmetrically, and whether the discloser reduces openness in response to how it lands.
Positivity reciprocity measures whether warmth is returned in kind and how quickly. It counts appreciation, affection, humour, and encouragement per participant, then examines whether a warm message is typically answered with warmth, with neutral logistics, or with nothing. The ratio matters less than its trend: a stable imbalance is a different signal from one that widened over the last several months.
A repair attempt is a message that tries to de-escalate or reconnect after tension: an apology, a check-in, an acknowledgement, or humour used to soften the exchange. Grey Mirror reports detected repair attempts per 1,000 messages. Where the underlying data supports them, following-repair and recovery counts are separate contextual signals; neither measure predicts a relationship outcome.
Responsibility avoidance is an implemented message-local classification. It counts messages whose language is classified as blame shifting, denial, excuse making, minimizing, or deflection and reports participant counts where available. It does not perform complaint-response sequence modeling or infer intent.
Read the layers
Visual guide updated
Read the count, comparison or timing definition used by the report.
Check the participant mapping, date window and available input behind the value.
Use the stated interpretation and limits rather than treating a number as a relationship grade.
Compare like with like across windows. Counts from different definitions or coverage ranges cannot be treated as the same metric.