Round-Based Cooperation Retrospective¶
Ritual — instantiates Iterative Reciprocity and Repeated Interaction
Reviews repeated cooperation cycles to update contribution expectations and repair trust.
A Round-Based Cooperation Retrospective is the scheduled pause where a group looks back together at the cooperation cycles it just completed and re-sets what it will expect next time. Its distinctive move is forward recalibration through shared sense-making: it is not a real-time response to any single defection and not a verdict on who belongs, but a periodic ritual whose output is a revised understanding — an updated picture of who is expected to contribute what, a fair accounting of why some fell short, and a refreshed collective narrative of how the cooperation is actually going. It is the venue where a contributor who quietly carried the load gets seen, where a member who lapsed can explain, and where the group decides that last cycle's expectations need to change before the next one begins. It repairs trust not by punishing but by making the recent history legible and adjusting the deal accordingly.
Example¶
A consortium of eight research labs shares a common data repository: each lab is expected to deposit its datasets and cell-line samples so the others can build on them. Between deposits the collaboration runs on good faith, and good faith frays — two labs mine everyone's data while depositing almost nothing, and the productive labs start to wonder why they bother. Once a year the consortium holds a cooperation retrospective. It walks the whole cycle in the open: what each lab pledged, what actually landed in the repository, and where the collaboration stalled for lack of a promised dataset.
Crucially, it hears context before it judges. One low-depositing lab had an instrument fail for four months and a grant lapse — a capacity shortfall, not a raid on the commons — and the group adjusts its expectation for that lab rather than branding it a free rider. Another had no such excuse, and next year's memorandum raises its deposit commitment explicitly. Everyone leaves with a shared, retold account of who carried the collaboration and a revised set of expectations for the coming year. No sanction is issued in the room; what changes is the deal and the story the group will operate under next cycle. The format borrows directly from the after-action review, which asks what was supposed to happen, what actually happened, and what to change next time.[n1]
How it works¶
- Run on a cadence, not a trigger. It convenes on a calendar (each release, season, or year), so slow patterns and quiet free riding surface that no single incident would raise.
- Sweep the whole cycle. It reviews the completed rounds in aggregate rather than reacting to one event, reading the accumulated record the group already keeps.
- Hear context before recalibrating. Members supply the story behind their record; the group distinguishes genuine inability from strategic withholding before changing anyone's expectations.
- Output revised expectations and a shared account. The deliverable is an updated obligation picture for next cycle plus a retold, common narrative of what happened — not a punishment and not a membership ruling.
Tuning parameters¶
- Cadence — how often the retrospective runs. Frequent cycles catch drift early but cost attention and can feel like surveillance; rare ones let resentment compound between sittings.
- Scope — whole population versus only flagged contributors. Reviewing everyone is fair and catches the quiet cases; reviewing only flags is faster but misses patterns no single incident named.
- Blame framing — how firmly the ritual is held to be about learning, not fault-finding. A blameless frame surfaces honest context; a punitive one turns the room silent or vengeful.
- Forward-binding strength — whether revised expectations are advisory or become the next cycle's committed obligations. Binding output has teeth but can harden a rough draft into a rule.
- Publicness of the retelling — how widely the shared account travels. Open retelling reinforces cooperative norms; over-exposure can shame members into disengagement.
When it helps, and when it misleads¶
Its strength is that it is the group's slow, reflective control. It sees the patterns the day-to-day misses, it gives context a hearing before consequences fall — the difference between "temporarily couldn't" and "chose not to" — and it lets contributors know their effort was noticed, which is what keeps the reliable from feeling like suckers. It is also where the reciprocity deal is legitimately renegotiated, so expectations track reality instead of ossifying.
It misleads in two directions. Run without candor, it decays into ritual theater — a recurring meeting that retells a flattering story and changes nothing — or curdles into a blame session that relitigates every lapse and teaches members to hide their shortfalls. It is also a lagging instrument: because it fires on a cadence, acute exploitation can run unchecked for a whole cycle before the retrospective even convenes. The discipline that guards against these is the after-action review's own: a blameless, evidence-anchored format focused on what to change next time, paired with a faster in-the-moment mechanism so the retrospective is never the only line of defense.
How it implements the components¶
contribution_obligation_map— its central output: a revised, agreed picture of who is expected to contribute what in the next cycle, updated against what the last cycle actually showed.capacity_adjustment_rule— by hearing context, it separates genuine inability (an instrument failure, a funding gap) from strategic withholding and adjusts expectations accordingly rather than treating them alike.community_memory_channel— the shared, retold account of the cycle refreshes a common narrative across the whole group of who contributed and where cooperation stalled.context_or_appeal_channel— the sitting is the venue where a member can explain a shortfall and have that explanation weighed before expectations reset.
It does not manufacture the repeated grouping that gives the review something to look back on (interaction_horizon, participant_continuity_anchor, shared_benefit_pool — that is Partner Continuity Assignment), nor execute the move-by-move answer to a defection (reciprocity_rule, defection_response_ladder, forgiveness_and_reentry_path — that is Tit-for-Tat Matching Rule).
Related¶
- Instantiates: Iterative Reciprocity and Repeated Interaction — the periodic sense-making step that keeps the reciprocity deal aligned with what actually happened.
- Sibling mechanisms: Partner Continuity Assignment · Tit-for-Tat Matching Rule · Contribution Ledger · Membership Standing Review · Time Bank or Service Credit System
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Round Based Cooperation Retrospective operates by convenes participants on a cadence to examine completed cooperation rounds and build shared learning. That concrete deployed or enacted form is Communication, Facilitation & Learning under the frozen taxonomy.
Nearest alternative: Assessment, Review & Assurance — Although Assessment, Review & Assurance can support this mechanism, the frozen evidence makes its operative form the act that convenes participants on a cadence to examine completed cooperation rounds and build shared learning; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; medium confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Repeated-game economics formalizes how prior-round behavior updates expectations and can sustain or erode cooperation. The explicit retrospective and trust-repair routine synthesizes that lineage with behavioral experiments, team learning, psychology, and group sociology.
Related originating lineages:
- Behavioral Economics — behavioral_economics contributes experimental evidence on incentives, expectations, and strategic behavior to the mechanism’s formative or independently convergent form; that contribution does not displace the primary economics_finance lineage.
- Organizational & Management Science — organizational_management contributes decision records, operating routines, knowledge reuse, and institutional learning to the mechanism’s formative or independently convergent form; that contribution does not displace the primary economics_finance lineage.
- Psychology — psychology contributes social learning, group regulation, trust, behavior rehearsal, and expectation to the mechanism’s formative or independently convergent form; that contribution does not displace the primary economics_finance lineage.
- Sociology & Anthropology — sociology_anthropology contributes ritual transition, group roles, institutions, identity, and collective practice to the mechanism’s formative or independently convergent form; that contribution does not displace the primary economics_finance lineage.
Review resolution: The blind reviewers disagreed on primary lineage (economics_finance versus organizational_management); authoritative or primary research supports economics_finance as the best historical origin. Repeated-game economics formalizes how prior-round behavior updates expectations and can sustain or erode cooperation. The explicit retrospective and trust-repair routine synthesizes that lineage with behavioral experiments, team learning, psychology, and group sociology. The cited NBER, The Evolution of Cooperation in Infinitely Repeated Games; NBER, Starting Small: Endogenous Stakes and Rational Cooperation directly supports the defining operation used in that choice. All independently supported contributing domains are retained without an arbitrary cap, while domain_reach=multi_domain records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
- NBER, The Evolution of Cooperation in Infinitely Repeated Games
- NBER, Starting Small: Endogenous Stakes and Rational Cooperation
Notes¶
It is easy to confuse this with Membership Standing Review, which is also a scheduled, collective sitting. The line is what each decides: the standing review adjudicates who remains a member in good standing and ratifies sanctions, so its object is membership and legitimacy; the cooperation retrospective adjudicates nothing about belonging — its object is the go-forward deal, updating expectations and repairing the shared story. A group can run both: the retrospective resets the terms, the standing review rules on who is still inside them.
[n1] The after-action review, formalized by the U.S. Army, is a structured retrospective built around four questions: what was supposed to happen, what actually happened, why the difference, and what to sustain or change. Its discipline — blameless, evidence-anchored, oriented to the next cycle — is exactly what keeps a cooperation retrospective from sliding into either theater or a blame session. ↩