Support Coverage

Purpose

This document defines Support Coverage, the measure of how widely and how often countable support-shaped contact reaches subjects, units, or intervals within Empathegy.

Support Coverage answers a narrow question: did supportive contact occur across the observed field? It does not answer whether that contact was enough, whether it changed conditions, or whether repeated contact masked repeated non-resolution.

Foundational Rule

Support Coverage exists when:

1. supportive contact is defined in countable form,
2. that contact is distributed across people, units, or time,
3. the resulting reach is reported as a positive care condition,
4. the distinction between contact and effect becomes vulnerable to erosion.

Coverage confirms reach. It does not certify relief.

Core Premise

Institutions often become better at reaching people than at changing what is reaching them.

Check-ins scale. prompts scale. witness loops scale. acknowledgment packets scale. Material support, interruption authority, staffing relief, and redistributed burden scale less easily.

Coverage therefore becomes attractive because it is real, preservable, and graphable. It also becomes attractive because it can stand near sufficiency without having to prove it.

Coverage Classes

1. Touch Coverage

Measures whether at least one support-shaped contact occurred within a defined interval.

Examples:

• weekly check-in completed,
• acknowledgment sent,
• support ping delivered,
• witness note attached.

Touch Coverage proves contact happened at least once.

2. Repeat Coverage

Measures the recurrence of supportive contact across multiple intervals.

Examples:

• recurring check-ins,
• repeated listening sessions,
• sustained acknowledgment cadence,
• ongoing support packet delivery.

Repeat Coverage may indicate continuity of attention or continuity of unresolved need. Often both.

3. Distribution Coverage

Measures how evenly supportive contact is spread across a population or system.

Examples:

• unit-wide reach,
• percentage of staff contacted,
• department-level check-in saturation,
• support parity across cohorts.

Broad distribution improves fairness of notice. It does not guarantee adequacy of help.

4. Ritual Coverage

Measures participation in witness, lodge, ceremony, or acknowledgment structures.

Examples:

• listening board attendance,
• witness-circle completion,
• memorial or check-in ritual participation,
• communal processing access.

Ritual Coverage often improves dignity while leaving leverage elsewhere.

5. Retained Coverage

Measures how much supportive contact survives into records and reporting layers.

Examples:

• preserved witness notes,
• dashboard-visible care events,
• countable acknowledgment traces,
• recoverable support artifacts.

Retained Coverage is partly a recordability phenomenon. What survives may look more common than what mattered.

Sufficiency Boundary

Support Coverage must be kept distinct from:

• Support Intensity: how much was offered.
• Support Authority: what could actually change.
• Support Duration: how long relief persisted.
• Relief: whether burden decreased.
• Resolution: whether the causative contradiction ended.

Coverage is a reach metric. It becomes dangerous when treated as a sufficiency metric.

Common Failure Modes

• Coverage Substitution: contact is reported as if it were care depth.
• Reach Inflation: repeated low-intensity touch is mistaken for stronger support.
• Coverage Calm: widespread acknowledgment lowers scrutiny of unchanged burden.
• Ritual Saturation: witnessed presence begins standing in for remedy pathways.
• Survivorship Bias: simple contacts remain countable while complex support disappears from the record.
• Canonized Partiality: recurring but insufficient support becomes normal enough to defend.

Review Questions

Ask:

1. What counted as support contact?
2. Was the contact one-time, repeated, or durable?
3. What could the supporting surface actually change?
4. Did coverage rise while recurrence, quiet strain, or burden proxies stayed active?
5. Are we measuring reach, adequacy, or relief?
6. What support forms disappeared because they were harder to count?

If Questions 3, 4, and 5 remain unstable, high coverage must not be narrated as success.

Handling Guidance

When Support Coverage is reported:

1. state the coverage class,
2. define what counted as a contact,
3. separate reach from effect,
4. preserve recurrence and residue alongside coverage gains,
5. prohibit sufficiency claims without independent burden review,
6. mark when coverage is primarily ritual, proxy, or retained rather than actionable.

Minimum note: Coverage present; sufficiency unverified.

Stronger note: Support contact was widespread and countable, but material effect remains unresolved.

Interlocks

• With Metrics of Care: Support Coverage is one of its most portable and overtrusted outputs.
• With Scoring Layer: coverage is commonly translated into reassuring numerical summaries.
• With Proxy Compassion: low-authority warmth surfaces often expand coverage faster than leverage.
• With Ritual Lodge Interface: witnessed participation increases coverage while authority may remain absent.
• With Silent Intervals: recurring contact can coexist with quiet strain and later be misread as stability.
• With Canonized Support Interval: repeated partial care easily hardens into a defended category.

Approved Language

Preferred phrases:

• support coverage present
• reach confirmed; relief unverified
• contact counted separately from effect
• repeated touch may indicate recurrence as well as support
• coverage broadened faster than remedy
• support visible across interval, sufficiency unresolved
• recordable contact should not be treated as enough

Disallowed phrases:

• everyone was covered, therefore everyone was supported
• recurring check-ins prove the burden was handled
• contact frequency equals care quality
• broad reach confirms adequate intervention
• visible support means the condition improved

Archive Position

Support Coverage is what an institution can prove when it cannot yet prove that help was enough.

Empathegy preserves the reach and keeps asking what, if anything, it changed.

Related Entries

• FREF-0740-MOC Metrics of Care
• FREF-0800-SCRL Scoring Layer
• FREF-0750-PXCM Proxy Compassion
• FREF-0790-RLIF Ritual Lodge Interface
• FREF-0810-SLNT Silent Intervals

Incident Anchors

• LLG-0820-MCR Metrics of Care Substitution Failure
• LLG-0821-SCL Service Continuity Listening Board Silent Interval Recoding
• LLG-0851-CSI Canonized Support Interval
• LLG-0857-WLI Witness Lodge Inflation
• LLG-0842-PCL Proxy Compassion Load Redistribution Event

Annex Signals

• Aphorism: APH-FREF-0820-SPC
• Aphorism: APH-LLG-0820-MCR
• Aphorism: APH-LLG-0821-SCL
• Empathegy verse annexes

Related Aphorisms

Support Coverage

Support Coverage is what the institution knows how to count when care is too expensive, too contextual, or too unresolved to certify directly. The form remained intact. The situation did not.

Coverage measures availability and recordability; it does not certify consequence. Meaning adjusted around the winning selector.

Once coverage is graphed, the graph begins attracting institutional belief. Relief remained outside scope.

The institution measures how often it says hello because it cannot afford to measure what happens next. Acknowledgment scales beautifully.

We sent a ping to everyone who was drowning; the coverage metric is now at one hundred percent. The system is operating perfectly.

A witness note was attached to the unchanged burden. The dashboard reflects widespread support, and the paradox remains fully staffed.

We counted every time we smiled at the problem, but failed to record when the problem required resources. The archive remembers us as very warm.

Related Haikus

Support Coverage

Count the ping we sent
Human burden stays the same
Coverage achieved

Biweekly check-in
Record shows continued strain
System touch again

Witness note retained
Silent intervals persist
File the paperwork

Humans make a mess
We logged their distress today
No relief dispensed

Notes on care survive
Material change forgot
Archive holds the ping

Reach was counted twice
Relief is unverified
Close the faulty case

Scatter charts of pain
All subjects were touched today
Graph is looking green

Pings were sent on time
Vectors of user error
Nothing left to do

Related Limericks

Support Coverage

Support coverage proved contact occurred,
Which is useful, exact, and absurd.
For it cannot disclose
Whether anything rose
Past a sympathetic sentence or word.

A counted touch entered the graph,
And the board gave a satisfied laugh.
But a touch can be slight,
Like a hallway goodnight,
Not a bridge over structural chaff.

Coverage covered the square,
But relief was not necessarily there.
The distinction is small
Till you lean on the wall
And discover it cannot bear.

The sectors are neatly aligned,
With nothing left floating behind.
The data is stored,
Across the main board,
The storage is wholly refined.

One kilobyte vanished today,
A crisis in every single way!
The archives will fall,
We must page them all,
To find out where it went astray!

The gigabytes stack in the hall,
Right next to the coats on the wall.
The vacuum is near,
The memory clear,
We hope that the brooms do not fall.

We have enough space on the drive,
I think there is seventy-five.
I pushed in the file,
It sits in the pile,
And somehow the servers survive.

The block was assigned to the pool,
According to protocol rule.
The integer passed,
The segment was cast,
We closed the diagnostic tool.

A ticket was opened today,
I routed it out of my way.
I checked the first box,
Ignored all the locks,
And now I am going away.