Edge-Native Agentic Orchestration: The Orchestration Daemon

Radio-Frequency Telemetry: Bluetooth Angle-of-Arrival (AoA)

True spatial intelligence requires absolute coordinate mapping of physical entities within the Sovereign Shell. Audio and video supply semantic context; radio frequency supplies mathematical coordinates. The orchestration layer uses Casambi Bluetooth Angle-of-Arrival (AoA) tracking, via exposed WebSocket APIs, to generate accurate real-time spatial positioning. [74]

In the AoA method the tracked entity — a physical asset, an employee badge, a medical terminal — transmits a direction-finding signal from a single antenna. [75] The signal carries a Link Layer field known as the Constant Tone Extension (CTE). [77] The Sovereign Shell's locator devices, equipped with rapidly switched antenna arrays, receive the signal and perform In-phase and Quadrature (IQ) sampling. [77]

The phase difference, $\Delta\phi$, between signals arriving at two antennas separated by distance $d$ is given by the formula [76]:

Where $\lambda$ represents the signal wavelength and $\theta$ is the absolute Angle-of-Arrival. [76] By rearranging this equation, the daemon computes the precise spatial angle [76]:

Aggregating these angles across multiple locators within the Sovereign Shell, the daemon computes a precise 3D coordinate intersection. These coordinates stream into the daemon alongside the structured JSON transcriptions from the Whisper models, fusing semantic intent with physical location.

Hybrid GraphRAG: Contextual Execution

The orchestration daemon continuously writes this fused data — text, timestamp, coordinate space — into the tenant's hybrid Graph Retrieval-Augmented Generation (GraphRAG) architecture. [80] A pure vector database is insufficient for agentic execution because it lacks ontological awareness: it can find similar text but cannot model relationships or strict hierarchical permissions. The orchestration layer therefore mandates a dual-database approach at the edge:

• Qdrant (vector database): used for semantic similarity search and rapid contextual triage of transcribed text. [80] To absorb high-velocity ingestion of live transcripts, Qdrant is deployed at the edge with a two-shard layout — a mutable shard for live writes and an immutable shard mapped to the HNSW (Hierarchical Navigable Small World) synced baseline. [81]
• Neo4j (graph database): used to store complex relationships, historical state, and spatial topologies. [80] Neo4j maps the enterprise ontology — which employees may access which systems, where specific terminals sit within the building geometry, and the hierarchical dependencies of corporate or clinical operations.

When the orchestration daemon identifies a trigger condition, it executes a hybrid retrieval. If the Qdrant database matches a spoken command — for example, "update patient file" — the daemon extracts the associated user and entity IDs and queries the Neo4j graph for the contextual relationships linked to those IDs. [80]

Crucially, the Neo4j graph correlates the speaker's current Casambi AoA coordinate against the authorized physical zone for clinical data access. If the user is authorized, the daemon spawns a localized agent. [82] That edge-native agent retrieves the relevant graph context, processes the localized decision through the tenant's air-gapped LLM, and executes the digital API call to update the clinical-trial file. [80]

The orchestration is entirely deterministic. Every agentic action is constrained by physical-proximity capability ceilings and hardware-evaluated identity rules. [48] If the Bluetooth AoA data places the speaker in the hallway outside the authorized acoustic perimeter, the daemon nullifies the execution request — physically preventing the action regardless of any software-level permission or API token the user may hold. Governance lives in the kernel, tied directly to physical space. [48]