01 WHAT BLACKWAVE IS
BLACKWAVE begins with a simple problem:
different devices should not be forced into fake uniformity.
A T-Deck Plus has a keyboard and LoRa radio. A K10 has cameras, microphones and sensors. A K230 has much heavier edge-compute potential. A T-Echo is useful because it can remain small and low-power. A Linux machine belongs in infrastructure.
BLACKWAVE allows each of them to specialize while exposing a common system boundary.
CAPABILITY EARNED BY EVIDENCE · DISCOVERY IS NOT AUTHORITY · THE NETWORK IS NOT THE SYSTEM
CAPABILITY OVER MODEL NAME
Hardware is represented by what is actually present and usable, not merely by a product label.
DISCOVERY IS NOT AUTHORITY
A device being visible does not imply permission to invoke sensitive capabilities.
TRANSPORT IS A SERVICE
Applications specify the behaviour they need instead of hardcoding LoRa, Wi-Fi, BLE, cellular or USB.
EVIDENCE BEFORE CLAIMS
A compile, hardware probe, flash, boot and physical validation are different evidence states.
02 SYSTEM ARCHITECTURE
Four layers. Each does one job. Transport and control are separate failure domains.
FR3K INTELLIGENCE
Hermes · Android · Operators · Automation
BLACKWAVE CORE
Identity · Capability Registry · Authorization · Sessions · Transport / QoS · Evidence · Telemetry · OTA · Recovery · Contracts
COMMUNICATIONS
Reticulum · LXMF · MeshCore · Meshtastic · LoRa · FLRC · Wi-Fi · BLE · ESP-NOW · Cellular · Ethernet · USB
PHYSICAL SYSTEMS
ABYSS · RELAY · NEXUS · SPECTRE · SCOUT · SIGNAL · VIGIL · CHRONOS · PULSE · PATHFINDER
THE NETWORK IS NOT THE SYSTEM.
03 BLACKWAVE FLEET
Ten roles. Nine in Contract v2. Each card shows canonical hardware, role, and evidence state. PATHFINDER is outside Contract v2 — represented explicitly.
04 CAPABILITY EARNED BY EVIDENCE
Every capability moves through evidence gates. A blocked gate stays visible.
05 CURRENT BUILD LEDGER
Verified 2026-08-29 full software build — packaging-only, no device written. Each line is a build gate, not a marketing claim.
Source: releases/2026-08-29-full-build/BUILD-MANIFEST.json · SHA-256 verified · fr3k/research-reconciliation@2c423c6
06 NOT ALL DATA IS THE SAME
Applications describe what the traffic needs. BLACKWAVE decides how the available system can carry it.
CONTROL
commands
approvals
configuration
EVENT
observations
alerts
state transitions
STATE
battery · position
current signal
current target
INTERACTIVE
terminal · keyboard
UI feedback
BULK
firmware · maps
logs · models · files
STREAM
audio · video
high-rate telemetry
Candidate transports →
07 RF ATLAS
One physical transmission may be seen differently by multiple observers. Each observation contributes what it actually measured.
Each observation may carry: observer ID · timestamp · timestamp uncertainty · location · location accuracy · frequency · bandwidth · spreading factor · coding rate · PHY · RSSI · SNR · frequency error · airtime · protocol · confidence · radio · firmware · antenna · transport
Observation types: Observation · SpectrumObservation · RangeObservation · AircraftObservation · BLEObservation
RTL-SDR and embedded radios may eventually contribute complementary observations. EVIDENCE: EMERGING
08 SPECTRE // EDGE ANALYSIS
SPECTRE is the BLACKWAVE K230 edge-compute tier. Control-plane services and realtime media are separated by design.
Reticulum · Atlas · MCP
networking · storage
camera · display · KPU · FFT · media · radio
BLOCKED Host-side SPECTRE tests pass. The full vendor media/IPC image remains BLOCKED until the external K230 SDK can be reproduced from a clean trusted provenance baseline. This is not presented as completed.
09 SCOUT // PHYSICAL AI
Two owned K10s sharing one logical model where appropriate — reflex stays local, reasoning moves upward only when useful.
SENSOR → LOCAL REFLEX → TINY MODEL → DEVICE LOGIC → EDGE ANALYSIS → HERMES
Low-latency safety remains local. High-level reasoning can move upward only when useful.
10 RESILIENT COMMUNICATIONS
BLACKWAVE does not force one protocol everywhere. Reticulum / LXMF, MeshCore and Meshtastic are complementary — BLACKWAVE itself is not a mesh protocol.
The transport path may change. The event should not have to.
11 INFRASTRUCTURE
Clearly separated from Contract v2 embedded targets.
RASPBERRY PI 500
- Reticulum services
- Atlas backend
- SDR tooling
- build / provisioning
- dashboards
RADXA PI 4C
- headless gateway
- persistent services
- radio interfaces
- backend / databases
GPD WIN MINI
- field engineering
- SDR workstation
- serial / debug
- development
RTX 3060 HOST
- heavier AI inference
- model training
- embeddings
- vision / RF ML
- CI / orchestration
INFRASTRUCTURE ≠ CONTRACT ENDPOINT
12 FOLLOW THE BUILD
Timeline entries are sourced from structured data — not hardcoded marketing copy.
NEXT PHASE
- isolate K230 SDK provenance
- create hardware probe layer
- back up devices
- staged flashing
- physical subsystem validation
- receive-only RF validation
- controlled RF validation
- first physical Reticulum network
13 HARDWARE VALIDATION
One of the core reasons to revisit this page. Explicit gates — no fake percentages. Horizontal scroll on mobile or tap a device to drill down.
Gates: BUILD · PROBE · BACKUP · FLASH · BOOT · DISPLAY · INPUT · STORAGE · POWER · RADIO RX · RADIO TX · NETWORK · OTA · RECOVERY · INTEGRATION
14 RESEARCH LEDGER
Every investigation ends with a decision: ADOPT · PORT · STEAL CONCEPT · MONITOR · REJECT · BLOCKED
15 RELEASES
16 FIELD NOTES / VIDEO
Organized into OVERVIEW · ARCHITECTURE · SYSTEMS · DEVICES · VALIDATION. Synthetic imagery is marked ILLUSTRATION where evidence context could be ambiguous.
BLACKWAVE IS BEING BUILT IN PUBLIC.
Every build can pass.
Every probe can disagree.
Every blocked gate stays visible.
FOLLOW THE EVIDENCE.