A space is a region of meaning that can contain other spaces. Its location, its readers, and what they're allowed to do to it are properties of that same space — described together by three sets, not three separate systems. Everything below is that one idea, applied at a different depth.
1 · Structural Geometry
The formal shape: a space as position, containment order, and an observer/mode/authority-indexed resolution. Where the sets above get their definitions.
2 · Cryptographic Layer
The instantiation: how "audience" stops being a permissions table and becomes a cryptographic fact — replication and readability pulled apart, key-wrapped sets, union and intersection over real identities.
NRP · Concrete Syntax
how the algebra becomes an addressable URL
Where audience stops being just math and becomes routable: group:name is an anchored shared space — the namespace is stable, membership moves inside it. surface[a+b] is a derived one — the namespace is computed from the member set itself, and stops resolving the moment someone leaves.
3 · Synthesis
Where structure and cryptography meet: privacy as something a space derives from its own definition, not something a platform grants it.
4 · Reactive Engine
The performance side: once relationships are real pointers instead of copies, one mutation only has to touch what actually depends on it.
Applications
built on the same kernel, not part of the numbered index above
Demos that put the same topology/audience/capability mechanics to work on a concrete scenario.
Full glossary