ParviRange docs — what we planned for the military

Chefe 2810 · private repo github.com/RBKunnela/ParviRange · compiled from existing plans only

Ideia central

Your empty private repo now has a docs folder. It is the planned military delivery — RAID-lab on their servers, Nightfall vs Defenders in the same cage, 12 public-class kits, local proof of who did what, classified overlay stays with them. Lab engineering already ran in our house. Nothing is installed at a ministry yet. Sales stay closed until export-control and doctrine sign-off. Allowed claim today: in engineering.

Six steps: gated offer, contract, bundle, install, operations, exit

O que foi entregue

  1. Pushed to RBKunnela/ParviRange — start at docs/README.md.
  2. What we deliver / refuse · 12 kits · six-step lifecycle · install ceremony · 18 gates · telemetry pack on close · price band (not an offer) · briefing words already written for the military room.
  3. Verbatim ministry + police one-pagers under docs/from-house/.
  4. No keys, no tarball, no classified archives, no new capabilities invented.
LayerStatus
Planned (this repo)Written now
Vendor lab (E1–E4)Evidence all_ok, 17 Aug
Customer siteZero deployments

O que mudou no meio do caminho

Nothing invented. I did not add code, kits, or a customer bundle. I copied the plan that already lived in the mapping, the MHC one-pagers, the runbook, the telemetry decision, and the military briefing pack.

O que falta

You: open the repo and say if you want FI/PT one-pagers, slide files, or the real air-gap bundle in a different private place (not this git — keys stay out).
Sales GO still needs named legal counsel + export review + doctrine sign-off — that was already the gate. I did not open sales.