-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Elliot edited this page Jul 28, 2026
·
5 revisions
This is the reference manual for VTOC Agent: its device firmware, desktop companion, browser flasher, supported hardware, and integrations. It is written for people first, while keeping technical details explicit enough to support repeatable implementation and review.
| If you want to... | Start here |
|---|---|
| Understand how the pieces fit together | Architecture |
| Install a reviewed firmware release | Getting Started and Browser Flasher |
| Build or recover the initial Heltec board | Board Bring-up |
| Add another ESP32-class board | Hardware Support |
| Use or help build the desktop companion | Desktop Client and Host-side VTOC Client |
| Understand device modes and related integrations | Modes and Controls |
| Publish, review, or audit a firmware release | Release Process and Trust and Accountability |
| Understand data and permission boundaries | Safety and Privacy |
- Architecture — components, boundaries, control flow, and integration roles.
- Getting Started — safe paths for installing, building, or evaluating hardware.
- Desktop Client — the companion application experience and container boundary.
- Host-side VTOC Client — capability contracts for the service behind the companion.
- Modes and Controls — standalone, Sentinel, Ragnar, Intercept, and TAK workflows.
- Hardware Support — what “supported” means and how to add a board responsibly.
- Board Bring-up — exact-board evidence, normal-image testing, and recovery testing.
- Safety and Privacy — radios, transports, data, and permission boundaries.
- Browser Flasher — release manifest and owner-authorized install flow.
- Release Process — the route from candidate build to flashable release.
- Trust and Accountability — source traceability, evidence, recovery, and public trust.
The repository foundation, browser flasher, release-evidence gates, and board
bring-up record are in place. v0.1.0-foundation is intentionally a
non-flashable prerelease. The first flashable image will require verified
physical-board evidence and a separate recovery image.
The browser flasher always requires the owner to choose a serial port. It must never silently select, configure, or flash a device.