Publish curated ServiceMap source from 203eba8143a0d195e80eb0abfd88b7388ca93e0c

PUBLIC_SOURCE_EXPORT.md

@@ -1,3 +1,3 @@
 # Public source export
 
-This source snapshot was generated from the private canonical repository at revision `b1b437d847564b37e62e2da253cd3f0dd4cda0ae`. It contains no private Git history or operational evidence. Changes are published from the canonical repository.
+This source snapshot was generated from the private canonical repository at revision `203eba8143a0d195e80eb0abfd88b7388ca93e0c`. It contains no private Git history or operational evidence. Changes are published from the canonical repository.

PUBLIC_SOURCE_MANIFEST.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "sourceRevision": "b1b437d847564b37e62e2da253cd3f0dd4cda0ae",
+  "sourceRevision": "203eba8143a0d195e80eb0abfd88b7388ca93e0c",
   "files": [
     {
       "path": ".dockerignore",
@@ -24,8 +24,8 @@
     },
     {
       "path": "README.md",
-      "sha256": "8887dc7df5db24b00873789961e855fe08c9a9ce992302cbf48745c50de34285",
-      "bytes": 4738
+      "sha256": "9092c2af29ae9b85339695743e5b66967fee7572f2b235461b6eb9af82db79a4",
+      "bytes": 5345
     },
     {
       "path": "backend/Dockerfile",

README.md

@@ -48,6 +48,12 @@ Open `http://localhost:1253`. Standard Compose runs the Python API and React fro
 
 The single-container Unraid build is provided by `Dockerfile.unraid` and `docker-compose.yml`. Review the socket/network mounts before enabling discovery. A read-only Docker socket mount still exposes a powerful Docker API boundary. Broker mode requires a dedicated registered identity and token file and deliberately has no socket fallback. AppOps enrichment is optional; configure your own endpoint.
 
+## Move from demo to live coverage
+
+Exit the synthetic demo, define one real service and its dependency, then select the probe appropriate to that component. Check the observation timestamp and supporting evidence before expanding the topology. Review discovered candidates before importing them into the canonical map.
+
+If a component stays unmonitored or unknown, check its probe configuration, reachability and freshness. A dependency edge describes impact relationships; it does not prove that both endpoints are healthy. Keep topology configuration and persisted incident history in your backup plan.
+
 ## Security and health semantics
 
 Protect the UI/API with network restrictions or tested OIDC configuration. Authentication is disabled by default; do not expose an unprotected deployment to the Internet. OIDC supports viewer/operator/admin roles when its issuer, audience and groups are provisioned. Discovery uses deployment-configured targets, not arbitrary browser-supplied targets.