How loicz/fieldlink works
FieldLink coordinates field reports between offline-capable team nodes, with local browser operation and synchronization when connectivity returns. The main workflow is an operator creating or updating a report in the browser; the UI calls the local daemon, which maintains durable report state and exchanges events with peers. The graph also preserves documented attachment transfer, offline maps, signed ZIP transfer, and optional radio/device integrations. Some daemon internals and integrations are unsampled, so their documented links are identified as such rather than inferred from module names.
Main entry points: runtime.cpp Daemon runtime · App.svelte Report console · common.py Local adapter API · radio.py Meshtastic adapter
Components 18
Operator interface
- Report console
ui/src/App.svelte - Local API client
ui/src/model.ts - Offline map view
ui/src/Map.svelte - ZIP transfer
ui/src/transfer.ts
FieldLink daemon
- Daemon runtime
src/runtime.cpp - Network transport
src/transport.cpp - Peer resolver
src/resolver.cpp - Signed events
src/event.cpp - Report and blob store
src/store.cpp - Bounded disk executor
include/fieldlink/runtime.hpp
Peer synchronization
- Mutual TLS sync
src/transport.cpp - Map package tooling
tools/map_pack.py
Field integrations
- Meshtastic adapter
adapters/radio.py - Device telemetry
adapters/devices.py - Local adapter API
adapters/common.py
Other components
- Field operator
- Other FieldLink node
- Meshtastic hardware
Connections 18
- Field operator → Report console: uses
README.md - Report console → Local API client: calls
ui/src/App.svelte - Report console → Offline map view: renders
ui/src/App.svelte - Report console → ZIP transfer: calls
ui/src/App.svelte - Local API client → Daemon runtime: requests API
ui/src/model.ts - Daemon runtime → Report and blob store: reads and writes
- Daemon runtime → Bounded disk executor: dispatches storage work
src/runtime.cpp - Daemon runtime → Signed events: handles events
- Daemon runtime → Network transport: serves through
- Network transport → Mutual TLS sync: implements
src/transport.cpp - Mutual TLS sync → Other FieldLink node: synchronizes
README.md - Daemon runtime → Peer resolver: resolves peers
- Report console → Report and blob store: uploads attachment chunks
- Report console → Map package tooling: uses installed maps
- Meshtastic adapter → Local adapter API: calls
adapters/radio.py - Device telemetry → Local adapter API: calls
adapters/devices.py - Local adapter API → Daemon runtime: calls local API
- Meshtastic adapter → Meshtastic hardware: exchanges summaries
README.md