Multi-Domain Ground Control Station

One console to fly drones, drive ground robots, sail boats, and dive underwater vehicles — all on one screen. Multi-domain from day one, license-clean, works air-gapped. No cloud, no vendor lock-in. This is the full build log, oldest question to newest answer.

8 posts TypeScript Electron MapLibre Apache-2.0 🔒 some sections gated
July 2026

Wiring the Command Pipeline: The Ticker Stops Being a Promise

I'd marked the command pipeline "designed, not wired" and said so plainly. This post closes that gap — every command now traverses RBAC → Safety → ROE → Authorization before anything moves. The architecture that made it a small change instead of a rewrite.

Read more →

Why TypeScript Now — and When I'd Reach for Rust, Go, or C++

Is the stack good, or should the whole thing be rewritten in something faster? For what this software does today, TypeScript isn't a compromise — it's the right fit. The other languages have a real place, but at the edges, and only at a concrete trigger.

Read more →
June 2026

Thinking Ahead: The Comms Layer, and a Polyglot Edge

A direction post, not a shipped-feature post. Resilient datalinks, gateways, a mission system, and integration through published standards — plus why the edge goes polyglot (Rust, Go, C/C++) while the core stays TypeScript.

Read more →

Zero-Trust: What I Actually Enforce, and What I Only Designed

Most security write-ups blur the line between what's enforced in code and what's on a slide. For a defense-grade console that line IS the deliverable. Here's mine drawn explicitly — enforced, designed-but-not-wired, and roadmap. Naming the gap is the point.

Read more →

Talking to Drones Without the Internet

Air-gap means no internet, not no communication. The two-channel model, the local bearers, and the one seam that lets any device plug in — plus the first real hardware adapter, a clean-room Tello driver. (The Tello is the proof, not the plan.)

Read more →

The Stack — and the Three Rules That Picked It

TypeScript, Electron, React, MapLibre — and the three hard rules that chose every one of them: license-clean, runs air-gapped, and dangerous parts impossible by type. The stack is downstream of the rules.

Read more →
May – June 2026

GCS Build Log: Days 0–6

The day-by-day journal — what actually happened. Docs, design tokens, the map going live, making it testable, a ghost bug that took three sessions, and why I wrote a design doc instead of code.

Read more →

Building a Ground Control Station from Scratch

Where it started. What a GCS is, why I'm building one from scratch, and why multi-domain and license-clean matter. Civilian, Apache-2.0, my own IP.

Read more →