Survivor Literacy

Some systems are built to see events, not architecture.

Courts, schools, HR departments, child welfare agencies—most of their tools are designed for questions like:

• What happened?
• When did it happen?
• Who did it?
• Is it a violation of a rule or law?

That works fine for things like:

• a punch thrown on the playground
• a missed visitation
• a late report
• a broken contract

But it fails completely when the harm is not a single event, but a repeating pattern.

Incident logic vs pattern logic

Incident logic asks:

• “Show me the worst thing that happened.”

Pattern logic asks:

• “Show me what always happens.”

Those are not the same question.

Example 1: The “nice” parent who never has a single big incident

Imagine two parents in a custody case:

• Parent A: occasionally yells, once punched a wall, once sent a nasty text.
• Parent B: never yells, never hits, never sends anything overtly abusive—but constantly:
• rewrites history
• flips blame
• withholds information
• uses the child as a messenger
• smiles in public and undermines in private

Incident logic sees:

• Parent A: “documented anger issues”
• Parent B: “no documented incidents”

Pattern logic sees:

• Parent A: dysregulated, but legible
• Parent B: coercive, destabilizing, and structurally unsafe, but hard to capture in a single “event”

So the system often concludes:

“Both parents have issues, but only one has clear incidents.”

And the pattern disappears.

Example 2: The “helpful” colleague who quietly sabotages

In a workplace:

• Colleague X misses one big deadline.
• Colleague Y never misses a deadline, but:
• “forgets” to CC people
• withholds key information
• reframes others’ ideas as their own
• subtly undermines reputations

Incident logic:

• Colleague X: “performance issue”
• Colleague Y: “reliable team player”

Pattern logic:

• Colleague X: needs support and structure
• Colleague Y: is quietly reshaping the power structure and harming others’ careers

Again, the system sees the visible event, not the invisible pattern.

Example 3: The child who “acts out” vs the child who collapses

In a classroom:

• Child 1: throws chairs twice a year.
• Child 2: never throws anything, but:
• flinches when adults raise their voice
• takes responsibility for everything
• freezes when conflict appears
• constantly scans adults’ faces

Incident logic:

• Child 1: “behavior problem”
• Child 2: “easy kid”

Pattern logic:

• Child 1: nervous system screaming in ways adults can’t ignore
• Child 2: nervous system screaming in ways adults can ignore

The system responds to the child who disrupts, not the child who absorbs.

Why systems misread patterns

Because they are built on:

• Forms that capture dates, times, and single events
• Policies that trigger only when a threshold incident occurs
• Training that focuses on “what happened” instead of “what always happens”
• Metrics that count incidents, not trajectories

So when someone brings pattern evidence, the system doesn’t know what to do with it.

It asks:

“Where is the worst incident?”

And if you can’t produce a single spectacular event, the pattern gets downgraded to:

“Interpersonal conflict”
“Communication issues”
“Different parenting styles”
“Personality clash”

What this looks like in real life

• A parent says, “Every time I set a boundary, they escalate, flip the story, and recruit allies.”
• System: “So… what did they actually do that we can write down?”
• An employee says, “They never attack me directly, but they constantly undermine me in meetings.”
• System: “Do you have a specific example of harassment?”
• A child says, “They’re nice sometimes and scary sometimes and I never know which one I’ll get.”
• System: “Has this adult ever hit you or called you names?”

The pattern is the harm.
But the system is only listening for an incident.

Why this matters

When systems only understand incidents:

• Subtle, chronic harm is invisible.
• People who name patterns look “dramatic” or “obsessed.”
• People who cause patterned harm look “reasonable” in snapshots.
• Children learn that only bruises count.

Pattern recognition isn’t a luxury.
It’s a safety tool.

Until systems learn to ask,

“What always happens?”
instead of only,
“What happened once?”
they will keep protecting the wrong people.

And they will keep misreading the ones who can see the pattern.

We Believe You

---

Apple Music

YouTube Music

Amazon Music

Spotify Music

Explore Mini-Topics