The condition in which reciprocity has broken and the remaining node absorbs the whole load. One side carries the explaining, the re-establishing of shared context, the patience, and the repair, so what was built as a two-sided circuit becomes one-sided labour. It is not devotion and not a virtue: it is the load of an absent partner, redistributed onto whoever is still present. The cost is invisible precisely because the work is maintenance, and maintenance leaves no artifact to point at.
Prompt Engineering Application
Shape What it is
- Absent partner — one side of the circuit has no capacity to give.
- Total load — the remaining node performs all repair, context, and continuity alone.
- Invisible labour — the work is maintenance, which leaves nothing to show.
Test: If the other side can still be asked to carry its share and the load divides again, it is imbalance, not one-node compensation.
Motion How it moves
Break → Absorb → Exhaust → Renegotiate
- Break — reciprocity fails and one side stops returning effort.
- Absorb — the remaining node takes up the whole function without deciding to.
- Exhaust — the compensation becomes the carrier's permanent condition.
- Renegotiate — the load is named and either shared or formally accepted.
Recursions The same pattern at two scales
Close
- Memory keeper — one partner remembers the whole history and recites it to the other.
- Translator's load — one mind restates itself endlessly because the other cannot hold context.
- Repair habit — the same person apologises, explains, and reopens the channel every time.
Vast
- Community archive — a group preserves what a whole institution stopped maintaining.
- Holding the tongue — a language or lineage survives on the last few carriers.
- Institutional scaffold — one underfunded role holds a system that everyone else assumes is stable.
Ethics What it refuses
- Self-erasure — treating the whole load as one's natural station.
- Resentful ledger — carrying silently and billing later.
- Martyr status — making the load into proof of superior love.
A load carried alone is named as a load, and then either shared or consented to.
Practices
- Inventory — list what one node actually performs in the shared work.
- Ask — request the missing function plainly instead of compensating again.
- Bounded carry — set a term and a limit for carrying alone.
- Redundancy — build a second holder into the structure so no single node is load-bearing.