Edge nodes
An edge node is the local participant that holds the tools, information and permissions needed for a particular task.
Follow the practical exampleList the compute, storage, power and connectivity available at the device. Package the specific engine, reference data and interface it needs. Local-first is meaningful only when the required operation can run without silently depending on an unavailable remote service.
Health answers whether a service responds. Readiness answers whether its dependencies allow the intended task. A successful task result answers whether the work happened. Present those separately so an operator is not asked to infer task completion from a green dot.
When a node reconnects, preserve local record identities and the source versions used. Reconcile competing changes explicitly. The global view should retain the difference between a locally recorded observation and an accepted shared record.
A field worker records an inspection while disconnected. The node saves evidence and a local result. Reconnection transfers that record and returns an acknowledgement linked to the same identity.
This explanation identifies the workflow and its boundaries; it does not claim a live operation.
KEDDEH WEB4 implementation and recovery runbook — source for the host integration described in this library, not certification of every industry application.
Related topic: Mission technologies. This is optional background, not a required next step.