Entity System Architecture

The entity system is a small core protocol and everything built on it: the extensions that add capability, the SDK that makes it programmable, and the application architectures on top. The core is mandatory; everything here is optional and composes.

Read this corpus as design space, not as the system. The core is the floor — what two peers must share to interoperate at all. Everything on this site sits above that floor, and the particular set here is the one this project needed, not the only set that could be built on the same core. A peer that takes some of these, or none, or writes its own, still meets every other peer at the substrate.

Canonical reference. Maintained in entity-system-architecture (the core itself is the separate Entity Core Protocol). The documents below are reproduced in full, with generated indexes over the corpus.

The map

The clearest way in is the structure itself — what depends on what:

→ References & Dependencies — the cross-spec dependency graph. The most depended-upon specs are the load-bearing core; the newest network/resolution specs are the leaves. Every spec links to its page, so the map is also the navigation: start at whatever you need and follow the edges. The folder layout is just an organizational tag — this is the real shape.

Browse by area

If you would rather walk the corpus by category:

• Extensions — the capability library (foundational tier, identity stack, network frontier).
• Guides — how to compose the extensions; patterns, not contracts.
• SDK — the programming surface over the protocol.
• Applications — the L5 conventions for building on the substrate.
• Reference — the whole-system overview docs.

Where each of these stands — what is settled, what is converging, and what is still a proposal — is tracked under Roadmap on the Entity Church Foundation front, which carries the extensions, SDK and applications roadmaps alongside the core protocol's.

The vocabulary

• Glossary — the terms this corpus is written in: each one defined, cited to the spec that defines it, and located at every place it occurs across the extensions.