Data substrate — not a peer plane
Triad
Node-owned operational data services that planes run on: relational truth, cache, vector memory, object storage, and message bus — bound to the deployment you control.
See also: Triad · Anchor Systems
Architecture
Presence is the ability for identity, intelligence, state, and authority to act coherently across physical boundaries.
That sentence is the architecture. PresenceOS coordinates identity, agents, workflows, models, memory, audit, and operational control for one reason — to keep those four coherent across the boundary you control.
Identity Passport / APIS
Intelligence Aether Gateway · Perceptor
State Triad substrate
Authority Mandates · RedWatch
Boundary Anchor · edge / on-prem / cloud / hybrid
L1
Identity
L2
Coordination
L4
Routing and access
L5
Audit and verification
Identity plane
Coordination plane
- CollabFabric
Agent coordination, discovery, messaging, registry, and trusted collaboration.
Built from MCP Fabric discovery and COLLAB messaging infrastructure.
Perception plane
- Perceptor
Vision, screen understanding, observation, and environmental awareness.
Routing and access plane
- Aether Gateway
Model, service, and tool routing.
- Aether Access
Scoped credentials, entitlements, and access control.
Audit and verification plane
- RedWatch
Immutable audit, policy enforcement, verification, and compliance evidence.
- RedWatch Sentinels
Persistent supervisory and threat-detection agents operating within the RedWatch lane.
Infrastructure plane
- Anchor Systems
The controlled infrastructure foundation supporting PresenceOS.
Naming discipline. PresenceOS is the operating environment. Anchor Systems are the infrastructure. Panel Room is the operator workspace (separate product surface — not this site). CollabGrid is a view inside Panel Room. CollabFabric is the backend coordination plane.
Maturity. Feature all planes as part of the architecture. Proof status lives on the homepage and research pages — do not invent GA claims.