About this article

• Audience: Integrators tracking Ghost Protocol firmware and platform releases
• Goal: Understand the current release train and where to find detailed release plans
• Type: Concept

Summary

Ghost Protocol ships edge firmware (Shadow hardware rc5), Phantom Vision orchestration, and verification harnesses as coordinated releases. The public site documents capabilities and operator procedures; wave-by-wave release checklists remain in private operator docs.

Current public baseline

• Shadow hardware: rc5 pricing tiers on ghostprotocol.us/capabilities
• Edge stack: RF-DETR person detection, H.265 justified recording, ONVIF MVP camera path
• Orchestration: Phantom proxy at :8788, MQTT fleet bus, soak automation tooling

Release verification checklist

1. Docs and manifest synced (npm run vet:docs in gp-site-v2)
2. Soak gates pass on canary shadow before fleet-wide promote
3. Public docs audit clean (no credentials, IPs, or live fleet IDs in shipped pages)

Next steps

• Production readiness — readiness themes (summary)
• Release plan — high-level milestones
• Contributing to docs — how docs ship with releases

Operator depth

Detailed release waves, gate percentages, and promote decisions are in private operator handoff (not published).