Reciprocity Log¶
Record and visibility tool — instantiates Reciprocity Protocol Design
A running record of who contributed what — and who benefited — that makes imbalance visible and remembered so it can be noticed and discussed, without minting credits or enforcing any rule.
A Reciprocity Log is a record whose whole output is awareness. It writes down who gave what and who received what, so that contributions stop being invisible and a lopsided pattern becomes something people can actually see and talk about. Its defining limit is as important as its function: the log issues no credits, sets no fair-exchange rule, and enforces nothing. It informs judgment and leaves the judging to humans. That restraint is what separates it from an accounting system — a log's entries are observations ("Priya covered three on-call shifts this month; Sam covered none"), not balances that can be spent or that automatically settle a debt. The log's value is that it defeats the failure mode where contribution goes unnoticed until a reliable giver quietly burns out — but it deliberately stops at making the imbalance visible, because turning it into an enforced tally is a different tool.
Example¶
Four housemates keep sliding into low-grade resentment over chores and shared costs. No one is a villain; the work is just invisible. Who last cleaned the bathroom? Who has been fronting the shared grocery kitty? Memory is unreliable and self-serving, so each person feels they do more than their share — a predictable effect of how vividly we recall our own effort and how dimly we recall others'. They start a simple shared log: a whiteboard and a notes app where each logged task and shared expense gets a line and a name.
The log changes nothing by rule and everything by visibility. Within a month the pattern is plain on the board: one housemate has logged nearly every deep-clean while another has logged almost nothing but keeps buying the shared coffee. The log does not declare anyone in debt or issue chore-credits; it simply makes the distribution legible enough to raise at a house meeting — "hey, the bathroom's been all me lately" — with evidence instead of a vague grievance. It also remembers: three months on, the housemate who carried the load during someone's exam week has that contribution on record, so the goodwill is not forgotten the moment the crisis passes.
How it works¶
- Records contributions and benefits as they happen. Each give and each take gets an entry, defeating the memory bias that makes everyone overweight their own effort.
- Surfaces the pattern, not a verdict. Aggregated entries reveal who gives and who takes over time, but the log stops there — it displays imbalance rather than ruling on it.
- Remembers past contribution. Entries persist, so a burst of generosity during someone's hard stretch stays on record and is not erased by recency.
- Leaves judgment to people. No credits, no automatic settlement; the log is an input to a human conversation, which is what keeps it a visibility tool rather than a ledger of enforceable debts.
Tuning parameters¶
- Granularity — every task logged versus only significant contributions. Fine granularity catches invisible work but risks tipping into oppressive tallying; coarse granularity is lighter but lets small chronic imbalance hide.
- Visibility scope — private to a facilitator versus fully shared with the group. Open logs maximize accountability but can breed score-keeping and defensiveness; restricted logs are gentler but reduce the shared awareness that motivates rebalancing.
- Memory window — how far back the record reaches. A long memory honors past generosity but can weaponize old grievances; a short window forgives but forgets who carried the load.
- Editorial discipline — what counts as a loggable contribution. A broad definition captures care and maintenance work; a narrow one is cleaner to record but silently devalues the invisible labor.
When it helps, and when it misleads¶
Its strength is that it turns a diffuse sense of unfairness into a shared, factual picture, which is the precondition for any honest conversation about rebalancing — you cannot repair an imbalance no one can see. And because it only records, it is cheap, low-commitment, and reversible.
Its failure mode is that visibility can curdle into surveillance and score-keeping. A log that tracks everything can transform warm, generalized giving into anxious balanced reciprocity, where people start refusing to help until their own column looks even — the very shift from open generosity toward tit-for-tat accounting[1] that anthropologists describe. The classic misuse is "ledger overreach": weaponizing the record to shame a member or to litigate every small asymmetry, which destroys the trust the log was meant to protect. The discipline that keeps it honest is to log at the coarsest granularity that still makes real imbalance visible, to frame entries as recognition rather than debt, and to remember that the log's job ends at making the pattern seeable — the repair is a human conversation, not a number to be settled.
How it implements the components¶
contribution_visibility— its core function: it records give-and-take so contributions and burdens that would otherwise be invisible become legible.imbalance_signal— aggregated over time, its entries reveal who chronically gives and who chronically takes, surfacing lopsidedness for people to notice.reputation_memory— entries persist, so past contribution (and past free-riding) is remembered rather than erased by recency.
It does not mint spendable credits as an exchange unit (exchange_unit), schedule deferred settlement (exchange_timing), or set an equal-hour balance rule (balance_criterion) — that is Time Bank or Credit System; a reciprocity log only makes imbalance visible for humans to discuss, where a time bank turns contribution into currency that settles automatically.
Related¶
- Instantiates: Reciprocity Protocol Design — it is the visibility-and-memory form of the protocol, making contribution legible without enforcing balance.
- Sibling mechanisms: Benefit-Sharing Arrangement · Contribution Norms · Cooperative Agreement · Exchange Protocol · Mutual Aid Rules · Partnership Agreement · Time Bank or Credit System · Reciprocity Check-In
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Reciprocity Log operates as a persistent ledger, log, register, or case record that preserves history and traceability because it a running record of who contributed what — and who benefited — that makes imbalance visible and remembered so it can be noticed and discussed, without minting credits or enforcing any rule.
Independent corroboration: The frozen evidence defines Reciprocity Log as 'A running record of who contributed what — and who benefited — that makes imbalance visible and remembered so it can be noticed and discussed, without minting credits or enforcing any rule', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: A non-monetized record of contributions and benefits makes social exchange obligations visible; accounting independently contributes durable ledger form without defining the reciprocal relation.
Related originating lineages:
- Accounting & Auditing — Ledger practice contributes durable recording and imbalance visibility.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of sociology_anthropology: A non-monetized record of contributions and benefits makes social exchange obligations visible; accounting independently contributes durable ledger form without defining the reciprocal relation. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
The reciprocity log is the natural upstream feed for several siblings: Mutual Aid Rules reads it to watch the give/take pattern, and Benefit-Sharing Arrangement divides by it. The design tension is that the moment a log's entries start being spent rather than merely seen, it has quietly become a time bank — and inherits that tool's very different risks of transactionalizing the relationship.
References¶
[1] Sahlins, M. Stone Age Economics. Aldine-Atherton (1972). Distinguishes open-ended generalized reciprocity from balanced reciprocity, which entails commensurate return within a finite period. registry ↩