Empathy Ledger
Stories are not content.They are relationships.
Empathy Ledger helps communities and organisations hold lived experience with its source, permissions, decisions and return intact.
The river is a way to explain responsibility: a source, boundaries, channels and a visible return.
Original Empathy Ledger river artwork
The problem
Too often, a story travels farther than the relationship that made it possible.
A recording can become a transcript, a theme, a report or a campaign. Along the way, source, permission and context can be separated from each other.
Empathy Ledger keeps those things together. It is not a publishing pipeline. It is a durable record of the relationship around a contribution, including when the answer is no or not yet.
How the system works
A story moves only through named, visible conditions.
The river model turns an abstract promise into a checkable path. Each point answers a practical question before anything moves downstream.
- 01
Source
A person begins the record
A contribution remains connected to who shared it and the context it came from.
- 02
Boundary
Permission sets the banks
Privacy, access, cultural instruction and correction paths remain beside the source.
- 03
Review
Meaning is not assumed
People review the evidence and the intended purpose before an interpretation is relied on.
- 04
Use
One named use at a time
A story can be considered for a specific audience, channel, purpose and period, not blanket release.
- 05
Return
The relationship remains visible
Agreed return, responsibility and evidence of delivery stay attached to the record.
One record, bounded views
The same record can be held with different responsibilities.
Empathy Ledger does not make one version of a story available to everyone. It keeps a shared source while making each person's legitimate view, limits and responsibility explicit.
01 / Storyteller
The source remains close
See the contribution, its permissions, proposed uses and the history of decisions.
Sharing is never assumed from participation.
02 / Community authority
Review has its own window
See the material and decisions that require community authority, without turning review into automatic access.
Authority is named for the specific record and purpose.
03 / Platform steward
Responsibility is visible
See what needs attention, the exact proposed use and the audit trail behind a decision.
Stewardship does not create blanket consent.
04 / Approved audience
Only the released view travels
A partner or the public can see only the material approved for that audience, purpose and period.
A release can be narrowed, expire or be withdrawn.
Release is a decision
A public story is a release, not a default.
Making something visible is an accountable decision about a particular use. It is never the automatic result of recording, reviewing or being part of the Ledger.
- 01
Private source
The record begins protected, with its context intact.
- 02
Named proposal
The audience, channel, purpose and period are stated plainly.
- 03
Human decision
The answer can be yes, no, not yet or a narrower alternative.
- 04
Permitted release
Only the agreed material is available to the named audience.
- 05
Visible return
Use, responsibility and agreed return remain attached to the record.
What the Ledger holds
The evidence for trust should travel with the story.
- Private is the starting state, not the exception.
- Permission is granular, reversible and recorded.
- A platform steward can act, but cannot turn ownership into blanket consent.
- A public account must be traceable to its source and the terms that allow it.
A practice of reflection
Good infrastructure makes room to listen before it acts.
Empathy Ledger is shaped by ACT's practice of Listen, Curiosity, Action and Art. It is a way to keep care, accountability and meaning together as a record moves.
- 01
Listen
Begin with the person, the place and the context around what has been shared.
- 02
Curiosity
Ask what a proposed use means before assuming that a story should travel further.
- 03
Action
Make the specific decision, responsibility and next step visible to the people involved.
- 04
Art
Translate approved knowledge into meaning without separating it from its source and relationship.
A public explanation, not public proof
The system can explain its rules without exposing the people it is designed to protect.
This page intentionally contains no storyteller profiles, quotes or case studies. Those belong here only when the named person and any required community authority have approved that exact public use.