Reference

The whole-system overview documents. They sit above the individual specs — orientation rather than normative text — and they are the way in when you need the shape of the system rather than the detail of one extension.

Canonical reference. Maintained in entity-system-architecture and reproduced here in full.

• Entity System Reference — the condensed working reference: the whole system in one document, written for someone already working with an implementation. The shortest complete picture.
• System Architecture — the layers, what lives at each, and where the boundaries fall.
• System Composition — how the core and the extensions compose into a working system: the emit pathway, cascade semantics, and state across a peer.
• System Identity Composition — how identity, attestation and quorum compose. Mostly orientation; its ownership-boundary section is normative for cross-implementation conformance.
• Identity Infrastructure — identity, authority and deployment read as infrastructure: what the identity stack assembles into once it is deployed.

Read the first for the picture and the last for the identity stack; the middle three are where a specific composition question gets answered.

Authoring standards

Not orientation — the conventions the specifications themselves are written to. Worth reading if you are writing an extension of your own and want it to read like the rest of the set.

• Specification Format — how a normative specification in this ecosystem is structured: the required sections, conformance language, and how versions and dependencies are declared.
• Identifier Naming Conventions — how identifiers are named across specs, wire formats and SDK surfaces.

For the specs these summarize, browse the Extensions, the Domain Patterns, or follow the References & Dependencies graph.