Service Status
Repository-built is not production-proven.
The current deployment is a private-alpha field system: one small server, one Daemongate, rootless containers, a genuine Tor control path, and explicit payment locks.
Failure evidence
Every interruption needs an observed record and a recovery record.
The lab harness must expose each failure separately and retain sanitized JSONL evidence before it reports success. Physical network, sleep/wake, and customer-router runs remain separate dated field evidence; repository tests never impersonate them.
Endpoint path changes
The direct check fails closed, then endpoint discovery and signed reconciliation restore it without selecting another data path.
EVIDENCE REQUIREDDestination sleeps
The outage becomes visible while destination components are paused, and the existing authority recovers after resume.
EVIDENCE REQUIREDWAN mappings disappear
Tor and WireGuard reachability vanish together, then return through explicit route reconciliation.
EVIDENCE REQUIREDControl delivery stops
Durable work reports retrying while Tor is unavailable and converges only after the authenticated path returns.
EVIDENCE REQUIREDManager and controller restart
Reachability loss is visible; durable keys, DNS, tunnel state, and bilateral policy must reconcile afterward.
EVIDENCE REQUIREDIntroduction UI disappears
The missing portal is visible, but an established direct relationship must continue without a central application fallback.
EVIDENCE REQUIREDRecording boundary
Retain scenario, observed/recovered phase, UTC time, run identifier, and bounded outcome only. Never put phrases, keys, endpoints, DNS queries, application requests, packets, or traffic content into failure evidence.
Current operating shape
Small enough to describe honestly.
The pre-alpha target has roughly 8 GB of available storage and one independently keyed Daemongate. It cannot claim regional redundancy, three-witness domain verification, general availability, or production continuity.
DaemonChat uses direct WebRTC data channels with no TURN relay or Tor streaming. 1Man carries short-lived room leases and encrypted signaling only. The tandem Daemonet preview uses the real Tor onion for managed authority access.
Incident posture
Failure must remain visible. If Tor, certificates, DNS, entitlement, identity, or routing fails, the service stops rather than changing access mode or trust model behind the user’s back.
Test the actual system