Edge-Native Agentic Orchestration: The Orchestration Daemon
Once ambient reality has been routed, transcribed, and structured into lightweight JSON by the ingestion pipeline, it requires a central logic unit to trigger autonomous action. This is the role of the orchestration daemon — a background process running continuously within the orchestration layer, acting as the deterministic bridge between spatial awareness and the tenant's Large Language Models (LLMs) and hybrid GraphRAG databases.
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, , between signals arriving at two antennas separated by distance is given by the formula [76]:
Where represents the signal wavelength and 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
- Memgraph (graph database): A native C++ in-memory graph used to store complex relationships, historical state, and spatial topologies. Memgraph maps the enterprise ontology and role-based access dependencies with sub-millisecond latency.
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 Memgraph graph for the contextual relationships linked to those IDs.80
Crucially, the Memgraph 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
Real-Time Stakeholder Augmentation
The purpose of the "Director's Cut" ingestion is not historical archiving; it is real-time capability expansion. Because the orchestration daemon fuses the visual graph, the acoustic transcription, and the spatial coordinates into Memgraph natively at the edge, it can execute zero-latency reasoning loops during the collaboration.
As external participants speak or interact with physical assets in the room, the orchestration daemon continuously queries the localized GraphRAG. If an external counterparty mentions a specific M&A precedent or hesitates on a contract clause, the localized AI instantly traverses Memgraph to find the organization's proprietary counter-arguments or related case law.
These insights are pushed via encrypted WebSockets directly to the authorized internal stakeholders' localized screens or Agentic Glass interfaces in real-time. The Sovereign Shell does not just protect the organization's intelligence; it actively weaponizes that intelligence, feeding the internal team the exact proprietary context they need at the exact millisecond the negotiation requires it.
Requirements formalizing this section
The narrative above is non-normative. The clauses below state the same architecture as testable requirements, and a conformance claim is evaluated against them rather than against the prose.
- ANM-7.1MUST · Class A, B
The orchestration layer of a conforming deployment MUST execute inside the demarcation boundary, including its policy evaluation, routing decisions, and scheduling state.
- ANM-7.2MUST · Class A, B
Every tool invocation available to an autonomous agent in a conforming deployment MUST be declared in advance, and an agent MUST NOT acquire a capability at runtime that was not present in its declared set.
- ANM-7.3MUST · Class A, B
Tool invocation through the Model Context Protocol in a conforming deployment MUST be authorized against the physical identity established under Chapter 8, and MUST be denied when no authorizing presence is established.
- ANM-7.4MUST · Class A, B
A conforming deployment MUST record every autonomous tool invocation with the invoking agent, the authorizing identity, the parameters supplied, and the outcome, and MUST retain that record inside the demarcation boundary.
- ANM-7.5MUST · Class A, B
A conforming deployment MUST classify tool invocations that mutate external state, transfer value, or communicate outside the organization as requiring explicit human authorization for each occurrence.
- ANM-7.6MUST · Class A, B
Retrieval assets built from tenant material — indexes, knowledge graphs, embeddings, and evaluation sets — MUST be stored inside the demarcation boundary and MUST be owned by the tenant.
- ANM-7.7SHOULD · Class A
A conforming deployment SHOULD express retrieval over typed relationships between people, documents, decisions, and events rather than over undifferentiated similarity alone.
- ANM-7.8MUST · Class A, B
A conforming deployment MUST interpose a policy and authorization engine between the agent and the Model Context Protocol server, such that no tool invocation reaches building hardware or clinical records on the model's authority alone. Policy MUST be externalized from both the model weights and the Model Context Protocol server, MUST be evaluated deterministically, and MUST default to deny.
- ANM-7.9MUST · Class A, B
A conforming deployment MUST treat all ambient capture, patient-supplied documents, and third-party correspondence entering the inference path as untrusted input with respect to agent authority, and MUST NOT allow instructions originating in that content to alter the agent's declared tool set, its authorization scope, or the policy governing it.
- ANM-7.10MUST · Class A, B
Transport between the agent, the policy and authorization engine, and the Model Context Protocol server MUST be mutually authenticated using short-lived workload credentials, and authorization MUST be expressed as fine-grained access control enumerated per tool rather than as a single privileged service identity.
- ANM-7.11MUST NOT · Class A, B, C
An implementation MUST NOT treat a discovery artifact such as an llm.txt file as a source of authority, capability, or policy. Machine-level execution MUST be carried by the Model Context Protocol and local programmatic endpoints, and a conforming deployment MUST operate fully with no discovery artifact present.