Ten open standards for coordination systems

Make coordination hold.

Every organization is built twice: once in intention, once in structure. The two drift apart, and when they drift, structure wins. CSIS makes intention and structure move in the same direction: ten open standards that find the failures every organization writes off as human nature, and repair them where they actually live.

10 standards1 structural model5-stage gap analysis5-minute startruns in any AICC BY 4.0, free

Solved at the structure

Conflict that keeps returningConflict Transformation

The trusted-insider exploitPower Obligation · Consent Legibility · Information Asymmetry

Burnout treated as a personal decisionFour Batteries · Regenerative Obligation

Rules that break at ten times the peopleCoordination Scaling

Power nobody is accountable forStructural Power Obligation

The warning everyone ignoredAdverse-Signal Engagement

Meetings that never make sense of anythingSensemaking

Rules so vague no one can break themPrecision-First Design

01The claim

Organizational failure is a structural problem. This is the structural answer.

Recurring conflict, exploited trust, burnout, opacity, collapse under scale: every organization meets them, and nearly every organization files them under human nature. Process gets tried and becomes bureaucracy; values get written down and change nothing; the retreat helps for a month. CSIS treats the same failures as engineering: each has a findable structural cause, a named standard that addresses it, and a specified repair.

The belief that a problem is just human nature is the problem's best protection, because a failure no one believes is structural is never examined structurally.

These recurrences are not weather. Each one is produced by something specific and findable in how the coordination systemtermAny arrangement where people combine effort toward something none could do alone: a team, a DAO, a nonprofit, a co-op, a company, a community. The word is deliberately broad; the failures repeat across all of them. is put together, usually by a load-bearing piece that is simply missing. Missing structure is invisible from inside, which is why the explanations keep landing on people. People are the only part you can see.

02One repair, worked

The insider who used the informality.

What happened

A community discovers that a trusted member has been quietly steering shared money toward their own circle for a year. The response is shock, then the question everyone asks: how could a person we trusted do this?

The structure under it

Wrong question. The right one: what made it possible for so long? Every safeguard was informal: good faith, reputation, the assumption someone would notice. The exploit did not defeat the structure. It operated where structure had never been built, and informality gave it a year of cover.

The repair

Not better people, and not surveillance. Make the visibility structural: who can move what, and who must be able to see it, stated explicitly, before trust is extended. The exploit needed the informality. Remove the informality it needed, and keep the trust.

That is one repair, and even this one draws on four of the standards at once: who can move what is power made legible, who benefits is consent made verifiable, the insider's unshareable view is a named information asymmetry, and "stated explicitly" is the precision discipline under all of it. The standards hold each other up, and why that is the suite's actual design is the next section.

03Structural integrity, for coordination

The engineering discipline organizations never had.

A bridge gets load calculations before anyone crosses it. An organization gets a mission statement and a retreat. CSIS closes that gap with the model engineers use for structures that hold through opposing forces, because that is what an organization is.

There is a class of structure held up by nothing you would expect: rigid bars that never touch each other, floating in a continuous net of cables. Engineers call it tensegritytermTensional integrity: a structure of rigid parts under compression (struts) that do not touch, held in shape entirely by a continuous network of parts under tension (cables). Remove one cable and the whole structure sags; the members hold each other up.. The bars push outward; the cables pull inward; each holds its shape only because the other is present. Remove a single cable and nothing snaps, but everything sags.

Coordination holds the same way. Some of what an organization needs pushes back against force: explicit limits, stated rules, structure that resists exploitation. These are the compressivetermThe suite's word for standards that resist force: they hold their form under adversarial pressure, the way a strut holds under load. Seven of the ten standards are compressive. members, the struts. And some of what it needs pulls the whole together: shared understanding, replenishment, the capacity to move through conflict rather than around it. These are the generativetermThe suite's word for standards that produce capacity rather than resist force: they carry tension the way cables do, connecting everything and keeping the rigid parts in relation. Three of the ten standards are generative. members, the cables. Neither kind works alone, which is the quiet reason so many past fixes failed: a strut was installed where a cable was missing, or the other way around.

Plate I · The struts never touch. The cables never slack. Remove either kind and the other cannot hold.

Compressive standards

Seven struts

Precision-First DesignThe suite's meta-standard: every term made operational, so a violation is detectable instead of arguable. All nine other standards rest on it.
Adverse-Signal EngagementThe unwelcome signal treated as a primary input, not noise to be minimized: engage it before it engages you.
Structural Consent LegibilityConsent you can verify, not just claim: who is acting and who benefits, made legible in every consent-bearing interaction.
Information Asymmetry ClassificationSix named classes of informational advantage, so the gap you could not name can be detected, challenged, and closed.
Structural Power ObligationPower measured on three independent dimensions, so concentration becomes detectable instead of indefinitely arguable.
Regenerative ObligationWhat draws on contributors' capacity must return it: proportional, in kind, and inside the relationship it drew from.
Coordination ScalingWhat holds at fifteen people breaks at fifty, and again at one hundred fifty; scaling is a structural event to design for.

Generative standards

Three cables

SensemakingThe discipline that produces genuinely shared language, so coordination is real rather than a coincidence of motion.
Four BatteriesPersonal, relational, contribution, mission: the four stores coordination runs on. Depletion is structural before it is personal.
Conflict TransformationMoving through conflict so it reorganizes the structure, instead of around it so it returns.

Hover either column and the plate shows you which members you are reading. The full text of every standard lives in the repository; the practitioner tools live one page in.

04Why one suite, and not one theory

The unity was found, not designed.

A claim that one framework solves coordination deserves your suspicion; frameworks that claim everything usually explain nothing. So it matters how this one was actually built: not downward from a theory, but sideways, one repair at a time. The same discipline of precision, applied to failure after failure across unlike communities, kept finding member after member of the same structure, the way the same load-bearing anatomy keeps turning up in funding programs that never learned from one another.

The suite is not a theory that predicts the ten standards. It is what accumulated when the same rigor kept being applied wherever coordination failed.

05What the whole structure stands on

Two commitments, held together.

The Coordination Structural Integrity Suite rests on two foundational commitments held together: precision and non-harming. Precision without non-harming becomes a control instrument: legibility in service of power rather than protection. Non-harming without precision becomes an attack surface: the good faith and informal trust that sufficiently adversarial actors exploit most reliably, operating in the spaces where formal instruments have no purchase. The fragility of those spaces is no longer a theoretical concern. It is the condition of the moment we are in.

Held together, they produce the structural conditions under which genuine presence is possible. For people who have been harmed by informality used against them, explicit structure is not a bureaucratic imposition. It is what trust requires before it can be extended again.

The precision is the compassion.

06What this does not claim

The edges, stated plainly.

The standards establish structure, not verdicts. They tell you what is missing and what holding it would require. Whether to build it, and what it is worth to you, stays your judgment; no standard here pretends to make it for you.
Structure does not replace trust; it is what lets trust be extended safely. A community that adopts these and stops trusting has misread them.
Adoption is voluntary and gradual. The standards are free, open, and usable one at a time (CC BY 4.0). Nothing requires the whole suite on day one; the plate just shows you what the missing members are doing to the ones you have.
Some problems really are people problems. The claim is narrower and sharper: before concluding that, check the structure, because from inside, the two are indistinguishable.

07Where to go from here

Start now. Free, open, five minutes.

Five minutes, any AI

Describe the problem. See its structure.

One prompt: paste it into the AI you already use, then describe the problem in plain language. It shows you what is structurally producing it, which standard repairs it, and the smallest first repair.

For the practitioner