Overview — What Is Structural Coherence?
This is the starting point. If you’re new here, read this first.
The Short Version
Structural coherence is the study of what must be true for a structure to hold together while it changes. SC-AS — the Structural Coherence Anchor Specification — is its specification: a closed set of formally defined terms, conditions, and rules, each stated with what it depends on, why it is needed, and why nothing weaker works. Together they state the conditions under which any structure holds together, changes without breaking, and produces genuinely new forms.
It applies to anything with internal relationships: physical systems, biological organisms, organizations, conversations, AI architectures, mathematical structures. It states what must be true for them to cohere, whatever they are made of.
SC-AS is published as an open standard by Coherence Research.
What Does the Specification Actually Say?
SC-AS is built from 76 formally defined terms. Every term carries explicit dependencies, a necessity proof (what breaks if you remove it), a minimality proof (why nothing weaker works), and an admissibility interface (where it connects to the rest of the system). Every assumption is stated in the text.
The core structural picture:
Configuration — any identifiable structure with internal relationships.
Adjacency — the relationships that define a configuration’s scope.
Driver — an internal differential, an unresolved tension within a configuration that creates the structural pressure for change.
Redistribution — change that resolves a driver while preserving adjacency and continuity.
Emergence — a redistribution that produces genuinely new structure, where the result cannot be mapped back onto the source.
Nonterminality — the requirement that admissible configurations with unresolved drivers must always have available pathways forward. Structure doesn’t get stuck.
This creates a precise picture: coherence is bounded, graded, and regulatory. A system can be more or less coherent. Incoherence is an admissible differential, provided it stays bounded and can be redistributed.
What It Starts From
SC-AS starts from structure alone: configurations, the relationships that define them, and how they change. It states structural conditions and leaves what things are, why they exist, and what they mean to the work built on top of it.
That starting point is what gives it reach. Because it commits to no particular substrate, domain, or scale, its conditions hold wherever structure holds — which turns out to be a very strong constraint set.
The specification is also self-verifying. It defines its own conformance criteria internally (AR11), so anyone can audit it for structural consistency using only the rules it provides. Its standing rests on checks you can run yourself.
Specification, Framework, Theory, Philosophy
SC-AS is a specification. Around it sit three other kinds of work, and we keep them apart because each makes a different kind of claim and is checked a different way.
The specification states the conditions a structure must meet to hold together while it changes. It is checked by conformance: does this structure meet these conditions? It changes only through a new versioned release.
A framework applies the specification to a particular job, such as a calculus for structural operations. Every framework names the SC-AS documents it is built on, and it is checked by derivation: does it follow from what it cites? Anyone can build one, and a flawed framework is fixed or retired while the specification stays as it is.
A theory explains why structures behave as they do under those conditions: how unresolved tension drives change, and why deeper structures have fewer forms open to them. A theory makes claims that can turn out false. Each claim is either derived from the specification or a stated premise the specification does not force, and it is checked by derivation and by evidence. A refuted claim revises the theory; the specification stays as it is.
A philosophy is the stance underneath all of it: describe structure before deciding what anything is made of, admit a claim only when what already holds requires it, and prescribe nothing. It is argued rather than tested, and it is why the specification is written the way it is.
Keeping them apart is what makes open research possible. Anyone can test a theory, build a framework, or dispute the philosophy, and the specification everyone checks against stays fixed. Anyone can discuss the work, submit to it, and build on it through our public repository; Coherence Research issues the official releases.
The Canonical Documents
SC-AS consists of four canonical documents:
SC-CORE — The complete structural kernel. 76 terms: 11 object-level primitives, 32 meta-definitions, 14 foundational conditions, 8 valid emergence conditions, 11 admissibility rules. Everything else derives from this.
SC-AXIOM — Ten canonical axioms (I–X) derived from the Core primitives. These establish the axiomatic consequences of the structural kernel — from minimal coherent excitation through hierarchy, information encoding, replication, and observation.
SC-HDR — The document header specification. Defines the metadata structure, integrity computation, and validation rules that govern every SC-AS artifact. The specification literally specifies how to verify its own integrity.
SC-SCOPE — The semantic scope and non-prescriptive clause. Defines what SC-AS claims, the canonical boundary, and the three-tier governance architecture.
Who Is This For?
Researchers who need a substrate-independent formal foundation for studying structure, emergence, coherence, or complexity — across physics, biology, cognitive science, organizational theory, or any other domain.
Engineers and architects who build systems that need to maintain structural integrity under change — AI systems, distributed architectures, organizational designs, protocol specifications.
Philosophers and theorists who want formally checkable structural foundations that carry no ontological commitments.
Anyone who wants to understand what it means for something to hold together, and what must be true for it to keep holding together while changing.
Scope and License
SC-AS is descriptive. It states the conditions under which structure holds, and leaves what exists, what is real, and what causes what to other work.
SC-AS prescribes nothing. What to build, how to organize, and what to value remain your decisions.
SC-AS is openly licensed. The specification is published under CC BY-ND 4.0. Anyone can read it, implement it, build on it, or test it. Implementations — including commercial ones — are unrestricted provided the specification itself is not modified or misrepresented.
Next Steps
Read the Specification →
The canonical documents with downloads, verification instructions, and release history.
Read the Founder’s Letter →
Why this work exists, where it came from, and what it’s trying to do.
Read the Release Announcement →
What’s in the Constitutional Release v1.0 and where to access it.
Test It →
The specification asks to be tested. If you find a structural issue, we want to hear about it.