From e4a07cf1e48b145f5eb74d09b147da25333ca961 Mon Sep 17 00:00:00 2001 From: anti Date: Sat, 18 Apr 2026 06:08:17 -0400 Subject: [PATCH] Design-Overview: correct embed-mode claim for collector/correlator/prober/mutator --- Design-Overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Design-Overview.md b/Design-Overview.md index b4056e9..1fe3831 100644 --- a/Design-Overview.md +++ b/Design-Overview.md @@ -43,7 +43,7 @@ For dev and for the smallest possible single-host deploy, two workers can run in - `DECNET_EMBED_PROFILER=1` — profiler starts in a thread on app startup. - `DECNET_EMBED_SNIFFER=1` — sniffer starts in a thread on app startup. -These are off by default in production deployments. The rest of the constellation (collector, correlator, prober, mutator) always runs embedded under the API as lightweight threads unless you explicitly shell out the standalone CLI. +These are off by default. The rest of the constellation (collector, correlator, prober, mutator) always runs as standalone processes — `decnet deploy` supervises them through a small process registry in `decnet/cli.py::_service_registry`, which respawns any unit that dies. Embed mode exists only for the profiler and the sniffer, which are the two workers cheap enough to live in-process during dev. ### The duplication risk