Why it matters
Built to stay up gives ForkMesh a concrete mechanism for operational guardrails for a node that may run for days. A crash handler, a UI stall watchdog, network backoff, and a network activity log keep long-running nodes healthy, and tell you exactly what happened when something hiccups.
A local-first forge needs the local app to be more than a mirror status screen. In ForkMesh, built to stay up addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles built to stay up through the same split it uses across the product: the Qt desktop node combines repo browsing, source control, worktrees, markdown, captures, shortcuts, diagnostics, and handoff flows around the hosted mirror.
The behavior is intentionally narrow: A crash handler, a UI stall watchdog, network backoff, and a network activity log keep long-running nodes healthy, and tell you exactly what happened when something hiccups. The same machine can hold the repository, review work, operate agents, and explain its own network state.
Where it fits
Use built to stay up when the machine hosting the code should also be the place where contributors understand and act on it.
It pairs with the rest of The desktop app because Built to stay up keeps operational guardrails for a node that may run for days connected to the repository, its signatures, and the nodes that serve it.