BRG · Internal Operator Console

GhostWire OS — Fleet & Deploy

The current OTA manifest is fetched through a fixed same-origin adapter. The remaining sections are operator references and target checks; they do not assert the present state of any handset or fleet.

OTA channel — checking… Field relay — check health Fleet cockpit — open
01

Deploy reference

verify the current repository scripts before execution

Full provision (USB, first time / hardware change)

Operator reference for update-phones.sh. Confirm the current script, Android tooling and handset authorisation in the GhostWire repository before running it.

# from the GhostWire provisioning checkout
export COCKPIT_PASSWORD='…' # enables fleet auto-enroll
bash update-phones.sh

Treat the command as a runbook pointer, not evidence that provisioning or enrolment has completed.

Publish an update candidate

Operator reference for publish-ghostwire-update.sh. A successful manifest read confirms only the published metadata; it does not prove a handset downloaded or installed the APK.

# bump versionCode in app/build.gradle.kts FIRST
bash publish-ghostwire-update.sh path/to/signed.apk "release notes"
Handset installation requires a separate device receipt. This page deliberately makes no claim about the latest on-device version.

Live OTA manifest

fetching ghostwire-updates.craig-45c.workers.dev/manifest.json …
02

Target build profile

verification checklist · not a current device inventory

Layer 1 — GrapheneOS controls to verify

Anti-seizure

  • Verify duress-PIN behaviour
  • Set and verify auto-reboot policy
  • Verify USB policy while locked
  • Verify bootloader and signing-key state
  • Verify per-profile storage policy

Built-in firewall

  • Verify per-app network policy
  • Verify per-app sensor policy
  • Verify storage and contact scopes
  • Record the tested OS build

Bundled apps

  • Verify the approved browser
  • Verify camera and PDF apps
  • Verify the attestation route
  • Record optional app-store policy

Layer 2 — candidate application profile to verify

GhostWireours

Candidate secure-communications component
  • Verify messaging on the target build
  • Verify voice and video on-device
  • Verify message-lifecycle and media handling
  • Verify vault, screen and QR controls

Mullvad VPN3rd-party

Candidate network-privacy component
  • Verify connection and leak tests
  • Verify the approved account policy
  • Verify DNS policy on-device

Pharoah Mobile Shieldours

Candidate cellular-signal component
  • Verify supported detections
  • Verify audit and travel modes
  • Verify any fleet reporting separately

Aegis3rd-party

Candidate authenticator
  • Verify storage and offline operation

KeePassDX3rd-party

Candidate password manager
  • Verify vault policy on-device

Orbot / Tor3rd-party

Candidate anonymity-network component
  • Verify routing for the approved apps
  • Record the tested configuration

Distribution candidate

Aurora Store3rd-party

Evaluate this route for approved third-party apps and record the tested account and update behaviour. GhostWire release metadata is checked separately through the live OTA manifest above.

03

Per-phone hardening profile

saves to this browser · do on the reference device, then clone

These are GrapheneOS Settings toggles (not all adb-settable). Nail them on one reference phone, photograph the settings, then replicate identically across the fleet.

04

Fleet management source

open the authenticated cockpit to verify current state

Open the GhostWire Fleet cockpit to verify devices, enrolment, billing and version state. This portal page does not fetch, copy or infer fleet records.

05

Gap register boundary

no cached operational status

No current GhostWire gap register is connected to this route. The previous static owner/status table has been removed so old assignments and device figures cannot be mistaken for live work. Use the owning repository and authenticated fleet cockpit as the current sources.