About this article

• Audience: Stakeholders and integrators who need a visual map before deep technical docs
• Goal: Understand how edge AI, recording, streaming, and fleet security connect at a glance
• Type: Concept

Summary

These executive diagrams summarize Ghost Protocol on Shadow 1: on-device detection and reasoning, justified edge DVR, optional WebRTC sidecar output, and a central proxy that ingests MQTT without exposing cloud keys on shadows. Replace PHANTOM_PROXY with https://<phantom-proxy>:8788. Roles use site-role-a and site-role-b.

Prerequisites

• Architecture overview for narrative tier descriptions
• Naming policy for canonical labels
• COTA POC bus topology for transit overlay (interactive + mermaid)

COTA bus AI overlay

For the 2026 COTA proof of concept (Axis + Shadow 2 + Phantom Vision), see COTA POC network topology — interactive Vue diagram plus mermaid source and PNG export.

1. Dual-model edge AI pipeline

On-device RF-DETR detections stay authoritative. Optional Gemma-class reasoning enriches events before MQTT publish—cloud APIs never run inside the sovereign oakapp.

Thermal governor throttles inference FPS before video encoding when die temp crosses 75°C.

2. Smart edge DVR

Justified 60-second H.265 chunks land in on-device storage with sidecar metadata. The proxy pulls playback-ready segments for operator review and optional cloud escalation.

Wall-clock chunk timing must match real time for downstream video APIs.

3. WebRTC and RTSP sidecar

A go2rtc sidecar bridges Edge AI TCP frames to RTSP and WebRTC for live preview—orthogonal to the justified recorder path.

Live preview does not replace justified chunk authority for escalations.

4. Enterprise security network

Shadows stay on the lab WLAN. The host runs MQTT ingest and the Phantom proxy; no shadow ships cloud API keys.

Hermes peer mesh (:11555) and mTLS sidecars (:8777) enable cross-shadow status without exposing raw device SSH.

Conventions

Label	Meaning
PHANTOM_PROXY	Central proxy base URL
site-role-a / site-role-b	Logical shadow roles
[operator-artifacts]	Harness output directory

Next steps

• Port-level detail: Architecture diagrams
• Recording contracts: Justified recording
• API probes: API quick reference

Operator depth

Live fleet state and harness evidence live in private operator handoff (not published) (private).