Appearance
Addressing
Pages in this section define the wire grammar and the identity stack underneath every Matrix subject. Read these in order if you are touching transport code, security policy, or routing. The Overview pages (Subjects, Mounts) cover the same material conceptually; this section is the formal reference.
| Page | What it covers |
|---|---|
| Subject grammar | The {root}.{mount}.$facet grammar with the verbatim transformation rules from NatsTransport.semanticToNats. |
| Authority roots | What "authority root" means; the public Space identity stack (spacePath, spaceId, authorityRoot). |
| Host wire roots | The Host's environment-level wire prefix (COM.NIMBLETEC.RICHARD-SANTOMAURO); how it is configured. |
| Runtime wire roots | Per-runtime scoped roots ({host-root}.{scope}); cascade rules when a runtime is in a sub-scope. |
| Mount claims | How a logical mount becomes addressable: registry claim, heartbeat, TTL. |
| Relative vs absolute addressing | Local-mount form (chat/$inbox) vs cross-root form (AI.HIVECAST.HOST/system.gateway.http/$inbox). |
Conventions used by these pages
- Subjects in code blocks are the wire form unless explicitly labeled semantic. The wire form is what NATS sees; the semantic form is what code outside the transport layer uses.
- Roots are shown UPPERCASE in examples for legacy reasons (the v1 root derivation produced uppercase roots). New Space
authorityRootvalues are lowercase (space.spc-7f3a9b2c); see Authority roots. - The terms "mount" and "logical mount" are interchangeable. "Local mount" is
system.registry's parameter name for the runtime-internal mount path used by a forwarding provider.
See also
- Subjects — conceptual overview.
- Mounts — the three names every live thing has.
- Subject naming reference — conventions for op and event names.