The standards.
All ten standards in full, at their current published versions, with the architecture that relates them and the vocabulary substrate they rest on. Everything is CC BY 4.0 in the standards repository; each entry below quotes the standard's own statement of purpose and links to its canonical text.
Why the suite has the shape it does.
The suite is organized on a tensegrity model. Seven compressive standards resist force: they hold their form under adversarial pressure, the way struts hold under load. Three generative standards produce capacity: they carry tension the way cables do, connecting everything and keeping the rigid members in relation. Neither class functions alone, and the architecture documents below derive the model, name the structural patterns it detects, and sequence adoption.
One standard is prior to the rest: the Precision-First Design Standard is the suite's meta-standard, and every other standard's conformance language is held to it.
Tensegrity Architecture
The model itself: why compressive and generative, and why each standard is where it is.
OverviewStructural Patterns Primer
The recurring dynamics the suite detects, named as patterns with their producing structures.
OverviewSuite Integration Guide
Adoption sequencing: what to install first and what each installation makes detectable.
OverviewDeployment Contexts
Five named standards configurations, matched to presenting situations.
Compressive standards
Seven struts"This standard addresses precision failure in two directions. A precision deficit occurs when instrument terms are under-specified: violations become undetectable and the gaps remain permanently exploitable. A precision imposition occurs when an instrument is over-specified: compliance can be demonstrated while the coordination purpose remains unserved."Abstract
In brief: the suite's meta-standard. Every term made operational, so a violation is detectable instead of arguable; all nine other standards rest on it.
"Adverse signals must be treated as primary inputs to coordination and security, not as nuisances to be minimized."Definition, §2.1
In brief: the unwelcome signal treated as a primary input, not noise: a structural obligation to engage it before the failure it predicts arrives.
"Every governance system claims to act with the consent of its participants. Very few can demonstrate it. The gap between claimed consent and verifiable consent is not a philosophical distinction. It is the structural condition through which extraction operates inside systems designed to prevent it."Purpose, §1
In brief: every consent-bearing interaction made legible along two axes: who is acting, and who benefits from the action.
"This standard specifies a six-class taxonomy as the precise structural answer: a framework that names the distinct information asymmetry conditions that coordination systems produce, enabling them to be detected, challenged, and structurally closed."Preamble, §1
In brief: six named classes of informational advantage, so the gap you could not name can be detected, challenged, and closed.
"Power in coordination systems accumulates across at least three independent dimensions: where formal authority sits, who has the practical capacity to coordinate and integrate decisions, and how interpretive work is distributed across the system."Purpose, §1
In brief: power measured on three independent dimensions, so concentration becomes detectable instead of indefinitely arguable.
"It establishes that extraction is a structural violation when it is not matched by a proportional regenerative return that meets three conditions: non-fungibility, proximity, and embeddedness in the relationship that generated the extraction obligation. It does not prohibit extraction; it specifies the conditions under which extraction is architecturally valid."Preamble, §1
In brief: what draws on contributors' capacity must return it: proportional, in kind, and inside the relationship it drew from.
"A coordination system that works at fifteen people will not work the same way at fifty. A system that works at fifty will face structural breaks at one hundred fifty that it is not designed to survive."Preamble
In brief: scale-blindness treated as a precision deficit; the thresholds named, and the conditions for crossing each one made a conformance obligation.
Generative standards
Three cables"Sensemaking is the process that produces shared language. This standard specifies what sensemaking must structurally provide in any coordination system, without prescribing method."Abstract
In brief: five structural invariants that distinguish genuinely shared language from assumed understanding, so coordination is real rather than a coincidence of motion.
"The capacity that coordination depends on, personal energy, relational trust, meaningful contribution, and alignment with purpose, depletes under sustained pressure without structural conditions for renewal. What gets named as individual burnout is often organizational infrastructure failure: the absence of structural conditions for regeneration."Purpose and Scope, §1
In brief: personal, relational, contribution, mission: the four stores coordination runs on, each with a charge and a developmental state the organization is obligated to condition for.
"Litigation terminates a conflict by producing a winner and a loser. Transformation converts the friction between parties into developmental signal, changes both parties, and strengthens the coordination medium rather than depleting it."Abstract
In brief: the structural preconditions under which conflict reorganizes the system instead of cycling; a companion specification covers readiness assessment before any process begins.
The vocabulary the standards rest on.
Under the ten standards sits Dimensional Frame Language: the foundational vocabulary specification that keeps the standards' own terms from importing structural assumptions their stated purposes do not intend. It is the discipline the suite applies to itself.