This is a real diagnostic of a real organization, produced entirely from publicly available data. The company is anonymized. The structural conditions are not.
How to read this
This is a weather map, not a report card. It measures the gap between what an organization says and what the world experiences. These conditions emerge from structure, not individual failure — but they persist because structure is left unchanged.
At a Glance
Overall Coherence
0.39
Elevated stress
Confidence
0.78
High
Data Quality
A
Strong coverage
Source Documents
69
Collection files across 7 source types
Claims Extracted
238
From organizational narrative
Observations Extracted
4,848
From external reality
The pipeline collected public data from SEC filings, earnings transcripts, job postings, employee reviews, customer reviews, social media, news coverage, and regulatory signals. It extracted what the organization says about itself (claims) and what the world says about the organization (observations). Then it measured the gap.
The Coherence Triangle
Organizational coherence rests on three vertices. When they align, the organization functions. When they diverge, structural conditions emerge that no amount of effort can compensate for.
Truth
0.44
Most stressed: omission
The gap between what the organization says and what is true. This organization's financial narrative aligns with performance. Its operational narrative does not.
Authority
0.38
Most stressed: compression
Who has the power to decide, and does it match who has the responsibility to act? Here, critical decisions are compressed into roles that can't resolve them at speed.
Continuity
0.35
Most stressed: displacement
Does the organization remember what it learned? Across 4 collection periods, Authority stress eased — but Truth degraded in lockstep. The condition migrated rather than resolved. The organization responded without learning.
Signal Velocity
Signal velocity measures how much heat an organization generates per document analyzed. It's the ratio of negative observations to total documents. A velocity above 50 is elevated. Above 100 is critical. This organization registered 176.
This entity
176.1
Peer A
105.7
Peer B
90.9
Peer C
71.0
Fleet avg.
49.7
Lowest
17.0
12,153 negative observations from 69 source documents. Each source document is a collection file — a batch of customer reviews, employee reviews, social media posts, or news articles. Individual reviews and posts within each file are extracted as separate observations. The ratio reflects an organization where a large, active customer base is generating signal at high volume. That signal isn't ambiguous. It's volume — the sound of a customer base telling the organization something it hasn't addressed in its public narrative.
Sustained Findings
The pipeline proposed 6 initial findings. An adversarial skeptic agent challenged each one across two rounds of debate. 2 survived. 4 were rejected. What follows are only the findings that withstood scrutiny.
Sustained — Truth: Alignment
Customer praise for the platform's usability aligns with center claims of a mobile-first, interface-focused product. Users consistently describe the experience as intuitive and accessible.
Decision authority for account restrictions and fund access is compressed into senior compliance roles. Frontline staff cannot resolve customer issues involving account freezes, holds, or access restrictions. Customers report being bounced between channels with no resolution path.
Note what the skeptic rejected: a finding about customer support omission (insufficient sample breadth), a finding about account freeze contradictions (lacking frequency data), a finding about diffused product ownership (limited evidence), and a finding about mission-to-operations misalignment (aspirational vs. operational distinction unresolved). The instrument doesn't assert what it can't defend.
Active Failure Modes
Across the full analysis period, the diagnostic detected 6 active failure modes — structural conditions that crossed the activation threshold at least once. Some have since receded as the organization responded. Others remain active. The cascade relationships between them tell the real story.
Operational responsibility concentrates at the execution layer without corresponding decision-making authority. In this organization, the compression point is compliance: critical actions affecting customer accounts require senior authorization, but the volume of cases exceeds the capacity of those roles. The result is a queue, not a resolution path.
Frontline teams carry the responsibility for resolving customer account issues but lack the authority to take action on freezes, holds, or restrictions. Customers experience this as being bounced between channels. Employees experience it as being accountable for outcomes they cannot control.
Escalation paths are functionally inverted — issues that should resolve at lower tiers are forced upward, while complex issues that need senior attention circulate without landing. 18 orphaned escalations and 9 bouncebacks suggest the escalation system operates as a holding pattern, not a resolution mechanism.
The shared story the organization tells itself about what it is and why it exists is fragmenting. Center claims emphasize a mission to democratize access, but edge observations describe a rigid, top-down operational structure with opaque decision logic. When the internal narrative diverges from external experience, coordination degrades because people are no longer solving the same problem.
Processes designed to manage risk have accumulated beyond their original purpose. What was built for regulatory compliance now extends into routine operations, creating friction at every customer touchpoint. The organization adds process to contain problems rather than resolving the structural conditions that produce them.
Individuals and teams compensate for structural gaps by extending beyond their defined roles. This creates short-term resilience but masks the underlying condition. When the compensators burn out or leave, the gap they were filling becomes suddenly, visibly catastrophic.
These six failure modes don't exist independently. FM-01 (Compression) feeds FM-03 (Responsibility Without Authority), which triggers FM-02 (Escalation Inversion). Simultaneously, FM-14 (Narrative Collapse) undermines the shared understanding needed to coordinate response, while FM-16 (Process Inflation) adds friction to every attempted fix. FM-06 (Adaptive Overreach) is what holds the system together — until it doesn't.
This is a cascade in progress, not a collection of independent issues. Addressing any single failure mode without understanding the chain will push the stress to adjacent conditions — which is exactly what the trajectory data shows happening.
Across a 15-entity fleet diagnostic, FM-01 appeared in 5 organizations. In the fintech sector specifically, it was detected in all three entities analyzed — suggesting a sector-level structural pattern driven by the intersection of regulatory compliance requirements and customer support scalability.
Precursor Signals
Field notes track signals that haven't yet reached failure-mode threshold but are moving in that direction. These are the early indicators — the conditions that, left unaddressed, become the next diagnosis.
FFN-10
Metric Displacement — 12 metric mentions against 3,195 complaints. Performance indicators may be replacing operational reality in decision-making.
Precursor to: FM-04 (Metric Shadowing), FM-11
FFN-16
Defensive Escalation — 20 observations where escalation is used for accountability transfer rather than problem resolution.
Precursor to: FM-02, FM-09 (Over-Escalation)
FFN-07
Orphaned Escalation — 18 unresolved escalation mentions with no designated ownership for resolution.
Precursor to: FM-03, FM-07 (Coordination Decay)
FFN-01
Compression at the Edge — 14 signals of responsibility concentrating at the execution layer.
Precursor to: FM-01, FM-02, FM-03
FFN-11
Context Gap — 56 mentions of results presented without interpretive frame. Outcomes are reported, but the conditions producing them are not.
Precursor to: FM-04 (Metric Shadowing)
FFN-21
Opaque Logic Drift — 11 observations where decision reasoning has become untraceable to those affected by it.
Precursor to: FM-04, FM-11
FFN-05
Escalation Bounceback — 9 observations of issues circulating through escalation channels without reaching resolution.
Precursor to: FM-01, FM-02
Continuity: The Condition Migrates
Continuity measures whether an organization retains what it learns. This entity was scanned across four collection periods as data quality improved from Grade C to Grade A. The coherence score is only part of the story. Watch where the stress moves — that's where continuity breaks.
Period 1
0.42
Authority stressed
Period 2
0.43
Authority critical · 5 FMs active
Period 3
0.49
Authority lowest: 0.375
Period 4
0.47
Truth now stressed
Between periods 3 and 4, the Authority score improved from 0.375 to 0.50. The organization appears to have responded to the compression pattern. But the overall coherence score dropped — because the Truth vertex degraded from 0.575 to 0.44.
The structural condition didn't resolve. It migrated. Authority pressure eased, but the gap between organizational narrative and operational reality widened. Financial metrics improved while 3,195 customer complaints accumulated against 12 metric mentions. The organization may be looking at the dashboard while the building is on fire.
What to Watch
Truth trajectory. The truth score fell 0.13 points in one period. If it continues, expect FM-04 (Metric Shadowing) to cross threshold — the condition where an organization optimizes for metrics that no longer reflect reality.
Metric displacement ratio. Currently 12 metric mentions to 3,195 complaints. If the ratio widens further, the gap between what the organization measures and what customers experience will become structurally invisible to leadership.
Escalation resolution rate. 18 orphaned escalations and 9 bouncebacks suggest the escalation system is functioning as a holding pattern, not a resolution path. Watch for escalation volume to increase as unresolved issues compound.
Authority recovery durability. The authority improvement (0.375 → 0.50) may be structural or cosmetic. If compression signals reappear in the next collection period, the improvement was a correction, not a fix.
Continuity trajectory. At 0.35, continuity is the lowest vertex. The next collection period will reveal whether the displacement pattern is a one-time adjustment or a chronic cycle — fixing one vertex by breaking another.
What to Say Monday Morning
A weather map is only useful if it changes what you do. Each question below is designed to surface the structural condition in the room — without blame, without accusation. These are the questions that make the invisible visible.
On Authority Compression
"How many customer issues right now are waiting on a decision that only one or two people can make? What would it take to resolve those at the frontline?"
Surfaces FM-01. Reveals the queue without naming it as a failure.
On the Narrative Gap
"What are we not saying publicly that our customers are saying loudly? What would change if we addressed it directly?"
Surfaces the Truth omission. Opens the door to honest communication without forcing a confession.
On Metric Displacement
"If we turned off the dashboard for a week and just read the raw customer feedback, what would we learn that we don't currently know?"
Surfaces FFN-10. Challenges whether the metrics are measuring reality or replacing it.
On Escalation
"When a customer issue gets escalated, who owns the resolution? Not who receives it — who is accountable for closing it?"
Surfaces FM-02 and FFN-07. Reveals orphaned escalation without assigning blame.
On Continuity
"Last quarter we addressed the authority problem. Did we track what happened next? Did solving one thing create pressure somewhere else?"
Surfaces the displacement pattern. The hardest question — it asks whether the organization learns from its own responses.
None of these questions accuse. All of them reveal. A leader who asks these in the right room will learn more in 30 minutes than a consultant will surface in 30 days — because the people who know the answers are already in the building.
What This Doesn't Say
This instrument measures structural conditions. It does not:
Assign fault. Failure modes are physics, not verdicts. They describe conditions that emerge from structure, not from individuals.
Predict outcomes. A low coherence score is a weather reading, not a forecast. Organizations with stressed conditions can and do recover — if they see the conditions clearly.
Replace internal knowledge. Public data reveals the gap between narrative and reality. Only people inside the organization know why the gap exists and what to do about it.
Claim completeness. The skeptic rejected 4 of 6 proposed findings. That's the instrument working as designed. What remains is what survived scrutiny — not everything that's happening.
Automated collection from public APIs and databases. No proprietary or confidential data. No inside sources.
Extraction
AI agents extract claims (what the organization says) and observations (what the world says) from each document. 5,231 total segments processed.
Scoring
Finding-derived scoring (v1) maps evidence to the Coherence Triangle. Agent-based scoring with adversarial skeptic debate. 2 rounds, 6 findings proposed, 2 sustained.
Infrastructure
Local compute only. No cloud inference. All models run on owned hardware. No data leaves the network.
Taxonomy
17 failure modes, 21 field notes, organized into the Coherence Triangle (Truth, Authority, Continuity). DRI™ framework v1.0.
Skeptic Agent Summary
"The findings are generally well-supported, but several rely on limited evidence and make assumptions that could be challenged. More comprehensive data would strengthen the conclusions."
The scan shows you the conditions. The questions help you surface them. But structural conditions don't resolve from awareness alone.
A Pre-Entry Diagnostic pairs the scan with a leadership evidence map — matching what the organization requires against what the incoming leader can verify they've done. For search firms, PE operating partners, and VP+ candidates evaluating a role.
A Coherence Sprint pairs the diagnostic with guided intervention — working with your leadership team to trace the cascade, prioritize the structural conditions that produce the most downstream damage, and design changes that resolve rather than displace. The scan is the map. The sprint is the expedition.