Current state stays separate from intent.
Build-tested, hardware-tested, field-validated, and production-ready remain visibly different claims.
Practical systems, built in the open
Practical tools.
Built with purpose.
Limited Underground is an open project workshop for practical software, vehicle tools, field hardware, and resilient communication systems. Each project has its own purpose, technology, evidence, and limits.
Active workshop
Projects with a practical purpose.
Each project has a clear boundary, visible status, and its own path from concept to useful product.
01TOffline group communication and awareness
Limited Underground Trail
Active development - single-pair BLE recovery tested
TechnologyESP32-S3 firmware, LoRa-class radio planning, BLE GATT, Kotlin Android, and a Windows loader inspection shell.Open project ->02SLinux server and dedicated LoRa network gatewayLimited Underground Trail Server
Clean VM reproduction and bounded API scaffold verified - reserved LAN and live radio pending
TechnologyDebian 13.6.0, a dedicated USB-connected Trail LoRa device, ASP.NET Core, PostgreSQL/PostGIS, Caddy, MapLibre, and PMTiles.Open project ->03DSupplemental vehicle data displayLimited Underground Display
Host-tested foundation - physical target pending
TechnologyC++17 telemetry components, CAN and J1939 parsing, normalized signals, display-neutral view models, alarms, and recovery contracts.Open project ->04HLocal-first vehicle analysis softwareHusky Performance
by Limited UndergroundProduct development
TechnologyWindows desktop software with local analysis, import, reporting, and packaged operator workflows.Open project ->05BPractical modular business operationsSmall Business Suite
by Limited UndergroundActive development
TechnologyWindows business software with local persistence, modular workflows, validation, reporting, and multilingual UI.Open project ->06FIdeas held until their boundaries are credibleFuture Projects
Exploration only
TechnologyNo stack is selected until a project has a bounded purpose and evidence plan.Open project ->Now, next, later
A clearer view of the work.
Progress describes what is proven - not how many files or commits exist.
The actual stack belongs with the project.
Software, languages when publicly confirmed, hardware, protocols, storage, and platform limits are presented in context.
Unfinished work remains visible.
Every active project names what is still untested, unavailable, or waiting for an evidence gate.
Build in the open
Follow the evidence - or help create the next piece.
Review repositories, contribute experience, and test compatible hardware when a project reaches that gate.