Reciprocity Agreement¶
Codified agreement — instantiates Social Capital Activation
Makes mutual expectations explicit — who may ask, what is owed, how to decline — so reciprocity builds reliability instead of coercive debt.
A Reciprocity Agreement codifies mutual expectations — who may ask for what, what counts as giving back, how to acknowledge, and, above all, how to decline safely — turning an implicit "we help each other" into stated terms. Its defining idea is that it is the codified terms, not the exchange itself: it is a lightweight social contract that makes reciprocity legible and refusal legitimate, and names the rhythm at which the terms are revisited. It provides no help of its own and connects no one; it sets the rules a network or a pair operates under. That is what separates it from a mutual aid network, which actually circulates the help, and from any person who carries the trust.
Example¶
A dozen families form a babysitting co-op. Left informal, it quickly sours: a few families always ask and rarely sit, and resentment builds without anyone naming it. So they write a simple agreement. Each hour of sitting earns one scrip token; each hour received spends one; everyone starts with the same handful of tokens. Two clauses do the quiet work: you may decline any request without giving a reason, and the group reconvenes each season to rebalance tokens and re-consent to the rules. The scrip makes reciprocity explicit enough that no family feels used, while the free-decline clause keeps a request from becoming an obligation, and the seasonal review keeps the terms alive rather than frozen. The agreement itself never provides a single hour of childcare — it sets the terms under which the co-op's help circulates fairly, and that is precisely its job.
How it works¶
- Name the terms. It states the ask, the give-back, the acknowledgment, and the exit — the parts of reciprocity that go wrong when left unspoken.
- Calibrate explicitness to the relationship. How formal the terms are is tuned to the stakes and the power difference, not set at one default.
- Make refusal first-class. A protected, non-retaliatory right to decline is written in, because that is what keeps reciprocity from becoming coercion.
- Set a review rhythm. The agreement names when its terms are revisited and re-consented, so they track the relationship instead of ossifying.
Tuning parameters¶
- Explicitness level — from an unwritten handshake norm to a tracked ledger. Too vague and people feel exploited; too explicit and help feels transactional. The right level rises with stakes and power asymmetry.
- Formality — a verbal understanding versus a signed document. Formality aids clarity and enforceability but can chill the very warmth that made help flow.
- Refusal strength — how strongly the right to decline is protected. Strong refusal rights prevent coercion but can be exploited by chronic takers.
- Balance tracking — untracked, lightly tracked, or fully ledgered. Tracking curbs free-riding but risks turning gifts into invoices.
- Review cadence — how often the terms are revisited and re-consented; frequent review keeps them current but adds ceremony.
When it helps, and when it misleads¶
Its strength is converting fragile goodwill into reliable, dignified cooperation: by naming who owes what and how to say no, it heads off the slow drift from generosity into resentment or obligation. In effect it is a deliberate choice of where to sit on the anthropological spectrum from generalized reciprocity (help with no expectation of return) to balanced reciprocity (a defined exchange), tuned to how much explicitness the relationship can bear.[n1]
Its failure mode is over-formalization: terms written so tightly that the exchange becomes a transaction and the relational trust that made help easy evaporates — the mirror image of the coercion it was meant to prevent. The paired danger is the dead-letter agreement, terms everyone signed and no one honors, which is worse than none because it manufactures false confidence. The classic misuse is dressing debt as reciprocity — using the language of a mutual agreement to lock people into obligations they cannot refuse. The guarding discipline is to keep refusal genuinely real and non-retaliatory, tune explicitness to the stakes rather than maximizing it, and revisit the terms on cadence instead of freezing the first draft.
How it implements the components¶
reciprocity_channel— it codifies the ask / offer / return / acknowledge route explicitly, so the channel's rules are shared rather than assumed.consent_boundary— it makes refusal a protected, non-retaliatory right and requires ongoing consent to the terms themselves.maintenance_cadence— it names the rhythm at which the terms are revisited and re-consented so they stay current with the relationship.
A Reciprocity Agreement does not implement resource_flow or bonding_tie — actually circulating help through a solidarity network is Mutual Aid Network's lane; the agreement only writes the terms — who may ask, what is owed, how to decline — that such a network, or any pair, operates under.
Related¶
- Instantiates: Social Capital Activation — the agreement is the archetype's answer to coercive reciprocity, making mutual expectations explicit and refusal safe.
- Sibling mechanisms: Trusted Intermediary · Mutual Aid Network · Peer Network · Bridging Organization · Partnership Broker · Community Connector · Warm Referral
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Reciprocity Agreement operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it makes mutual expectations explicit — who may ask, what is owed, how to decline — so reciprocity builds reliability instead of coercive debt.
Independent corroboration: The frozen evidence defines Reciprocity Agreement as 'Makes mutual expectations explicit — who may ask, what is owed, how to decline — so reciprocity builds reliability instead of coercive debt', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Norms of reciprocal obligation are foundational topics in anthropology and sociology.
Related originating lineages:
- Law & Governance — Agreement forms materially add explicit scope, refusal rights, and enforceable expectations.
Review resolution: Both blind reviewers agree that sociology_anthropology is the primary origin. Explicit reconciliation of domain reach disagreement, encyclopedia synthesis disagreement adopts reviewer_a's classification because norms of reciprocal obligation are foundational topics in anthropology and sociology. The resulting lineage records alternates=law_governance, origin_mode=cross_disciplinary_synthesis, and domain_reach=universal; these describe formative provenance separately from later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Marshall Sahlins' typology of reciprocity — generalized (giving with diffuse, unbookkept expectation of return), balanced (a defined, roughly equivalent exchange), and negative (attempting to get something for nothing). A reciprocity agreement is essentially a choice of where on that spectrum to place a relationship, made explicit. ↩