ABYSS
T-Deck Plus
esp32-s3
PROBED/PARTIAL
no artifacts
CAPABILITY · EARNED · BY · EVIDENCE
BLACKWAVE
// DEVICE DEPLOYMENT TERMINAL
IDENTIFY · VERIFY · FLASH · PROBE · VALIDATE · RECOVER
WAITING FOR HARDWARE // connect a target via WebSerial or WebUSB to begin — or pick a device below to inspect the manifest
// 01 Targets
Eleven contract devices and one infrastructure host. Every card shows the reconciled evidence state from docs/research/current-state.md — no state is ever promoted without matching machine-readable validation data.
RELAY
T-Deck Pro 4G
esp32-s3
PROBED/PARTIAL
no artifacts
NEXUS
M5Stack Tab5
esp32-p4-esp32-c6
PROBED/PARTIAL
no artifacts
SPECTRE
T-Display K230
k230
BLOCKED
no artifacts
SCOUT
UNIHIKER K10
esp32-s3
BLOCKED
no artifacts
SIGNAL
T-Embed CC1101
esp32-s3
PROBED/PARTIAL
no artifacts
VIGIL
T-Watch Ultra
esp32-s3
PROBED/PARTIAL
no artifacts
CHRONOS
T-Watch 2020
esp32
PROBED/PARTIAL
no artifacts
PULSE
T-Display S3
esp32-s3
PROBED/PARTIAL
no artifacts
PATHFINDER
LILYGO T-Echo
nrf52840
BLOCKED
no artifacts
INFRASTRUCTURE
Raspberry Pi 500
not a flasher target
CLAIMED/SOURCE_CONFIRMED
Pi 500 is infrastructure inventory. Image-writing would be a separate, deliberate workflow with a different threat model (full-disk image, not flash partition).
// 02 Recovery & Safety
Every device gets a recovery card. The flasher will never silently:
FLASH SUCCESS
...when only the download succeeded. Verifies the artifact before reporting success.
DEVICE VERIFIED
...when only a USB VID/PID matched. Carries a confidence score; AMBIGUOUS halts the flow.
SUPPORTED
...when the exact hardware revision has not been established. Revision detection is a separate evidence class.
NEVER MODIFY
eFuses, permanent security bits, calibration, private keys, identity region, RF transmission — default denied; explicit operator approval required.
// 03 Operating principles
Local-first. The browser app will not silently send serial logs, device identifiers, flash dumps, Wi-Fi credentials, keys, or configuration to FR3K servers.
- Discovery is read-only metadata about a peer; it never enrolls or authorizes a peer.
- Transport and control are separate failure domains; optional AI does not weaken the underlying system.
- Every artifact has a SHA-256. HASH VERIFIED is not the same as SIGNATURE VERIFIED.
- Hardware claims require hardware; LAN acceptance is never relabelled as RF, robotics, or field acceptance.
- Useful failure reports beat polished fiction. A blocked gate is a valid engineering result.