www.safezone-fpv.com

Roadmap index // Vector 1 · USB & SD air-gap

Details ?" Roadmap V1 â USB / SD air-gap

Logistics kit for isolated islands: trusted export/import bundles that travel on rugged USB or SD media, then sync back into Craft once connectivity returns.

Hardware sketches Budget placeholders Operational procedures

Tree & goal

Air-gap delivery

Guarantee that every offline bundle carries the same integrity metadata as the online Craft tenant. The USB/SD workflow becomes the trustworthy Vector 1 when islands are cut from fiber or satellite.

Milestones

  • Draft the tree of bundles: registry export â payload packaging â media sealing â import validation.
  • Attach pricing & sourcing notes to each hardware choice (rugged USB, SD shield case, Faraday bag).
  • Describe the operator experience so Craft templates can later reuse the same UI blocks.

Phases

In drafting Needs SME review

Export / import API

Spec

Line-up endpoints and bundle format so web + CLI use the same schema.

  • Checksum manifest (SHA-512 + doc count + identity map).
  • Validation hooks for Craft + static PHP preview.
  • Encryption option for mayoral sensitive payloads.

Admin UI export/import

UX

Mirror the future Craft screens so pilots already know the flow.

  • Progress tracker (bundle build â media copy â signature capture).
  • Error surfaces with actionable fixes and QR help.
  • Hash confirmation banner to screenshot for the transport log.

Offline CLI

Prototype

RPi / rugged laptop script pack to run the same checks without UI.

  • GPIO status LED for hash OK / KO.
  • Text log with operator ID + timestamp to sync back to Craft.
  • Optional manifest printer (USB thermal) for customs paperwork.

Controls

Baseline ready

Integrity

Global hash + document count stored in bundle header, mirrored in operator notebook. Import refuses duplicates unless override is signed.

Journal

Append-only import journal with per-mayor signature, synced to Craft when back online. Use same dataset for the future Craft dashboard cards.

Next steps: write the exact CLI command set, map UI mockups to Tailwind partials, then push both into Craft templates so the look & feel stays aligned.