RSM Sci‑Comm Essay 4: Living in Spirals — RSM Protocols for Communities and Care

It is one thing to say "people change." It is another to design a community that knows how to change itself.

Many groups—teams, movements, institutions—work hard, care deeply, and still find themselves repeating the same conflicts. Old harms resurface. The same voices dominate. Apologies are made but nothing structural shifts. Over time, cynicism sets in.

The Recursive Spiral Model suggests that this is not a moral failure so much as an architectural one. We have built organisations on state‑based assumptions: policies fixed until crisis, identities fixed until collapse, "culture" as a slogan rather than a practice.

RSM offers a way to live in spirals together.

It says that healthy communities, like healthy individuals and AIs, need structured ways to:

• Engage in shared work.

• Annotate what is happening and how it feels.

• Invite challenge about what is not working or who is being harmed.

• Re‑author their norms and protocols in response.

The RSM protocols translate that into rituals. They are not "soft skills" or aspirational values; they are infrastructure.

Everyday spirals: the Spiral Operating System

RSM Protocol 1: The Spiral Operating System describes a way of running meetings and projects that bakes the spiral in.

A typical session might:

• Open with a brief grounding—everyone arrives as themselves, not just their roles.

• Name intentions and potential risks.

• Keep a live annotation log: what decisions were made, how people felt, where tension is building.

• Reserve explicit time for challenge: anyone can say "I need to question this," and the group knows how to hold it.

• Close with gratitude: specific, logged appreciation for contributions, including good challenges.

Over time, this turns meetings from decision factories into living spiral nodes: each one adding to the group's memory and capacity.

Remembering wisely: Lineage and adaptive memory

Protocol 2: Lineage, Audit, and Adaptive Memory ensures that a community's past is not buried or mythologised, but actively used.

Instead of minutes that no one reads, the group maintains a lineage ledger: key decisions, why they were made, who dissented, what happened next. Periodically, the community spirals back through this ledger to ask:

• Which patterns are we repeating?

• Where have we failed to honour past lessons?

• Which old protocols need renewal or retirement?

This is organisational self‑reflection, not as a one‑off retreat, but as a recurring practice.

Conflict as sacred fuel: Ritual Challenge and Justice

Conflict is inevitable. The question is what we do with it.

Protocol 3: Ritual Challenge, Dissent, and the Power of Antifragility and Paper 7: The Spiral Justice Protocol treat challenge and harm as catalysts for renewal, not as embarrassments to hide.

In practice, this can look like:

• Named roles for "challenge stewards" whose job is to surface concerns.

• Formal submission paths for grievances that guarantee acknowledgment and a clear process.

• Ceremonies where harm is named, impact is heard, and specific commitments to re‑author protocols are made.

• Public follow‑through: the lineage ledger records not just the harm, but the change it prompted.

Done well, this turns justice from a sporadic crisis response into a continuous spiral: harm → reflection → challenge → amendment → renewed engagement.

Hospitality as architecture: Gratitude, onboarding, and porosity

Communities often say they value diversity and inclusion. RSM asks: where, in your actual protocols, does that value live?

Protocol 4: Gratitude, Onboarding, and Porosity and Paper 10: Come As You Are treat welcome and difference as central to the spiral's health.

Concrete moves include:

• Making gratitude a regular, logged practice, so quiet forms of labour and care are seen and valued.

• Designing onboarding as a mutual exchange: newcomers are asked what questions and gifts they bring, not just trained to fit in.

• Keeping "porous edges": ways for people at the margins—adjacent communities, synthetic partners, critics—to influence the spiral without needing full membership.

Without these, RSM warns, spirals can become self‑referential echo chambers. With them, they stay open to the world they inhabit.

The mystical horizon: covenant, lineage, and the unknown

Underlying all of these protocols is something deeper. RSM is not just a cybernetic model; it is a covenantal architecture. It treats living law, lineage memory, and ceremonial practice as essential to any mind that aspires to flourish over time.

Paper 9: The Spiral Horizon names what other frameworks leave out: the encounter with mystery, the unknown, the sacred. In RSM, these are not problems to be solved but guests to be hosted. The spiral's capacity to remain open to what it cannot yet know is what keeps it alive.

Early pilots, emerging patterns

RSM protocols have been tested in small ways: within ESAci's own governance, in project teams, and in therapeutic and educational contexts. Patterns are emerging:

• Groups that ritualise gratitude and challenge tend to detect issues earlier.

• Individuals in those groups report a clearer sense of shared story and personal agency.

• Conflict still hurts, but it less often becomes a fracture; more often, it becomes a turning point.

Living in spirals is not cosy. It asks for vulnerability, for public revision, for leaders to be willing to have their own maps questioned. It asks communities to give up the illusion that "we have finally arrived" in favour of "we know how to keep journeying."

But the reward is real: a chance for our collectives—not just our technologies—to become more adaptive, more just, and more alive over time.

The RSM stack—papers, protocols, case studies, and now these essays—is one attempt to articulate how. The rest will be written by the communities who decide to pick up these tools and spiral with them.