Publish curated ITWorx-Pulse source from 1b456e5a2e8bd0a3bb4238cdc3036b64a7690ae6

README.md

@@ -54,6 +54,12 @@ flowchart LR
 
 The web/API tier has no Docker socket or host-root access. Only the agent receives explicitly configured read-only sources needed for observation. PostgreSQL stores configuration, inventory, dashboards, alerts and audit; the worker handles discovery, probes and notifications.
 
+## Read a board with its evidence
+
+Start with the local mock environment to learn the board and incident views. In a real installation, configure the intended telemetry sources, then inspect timestamps and coverage alongside each status. Follow an incident into its supporting observations before deciding which infrastructure action to take.
+
+Unknown or stale observations need investigation; they are not a healthy measurement. A running Pulse container does not prove that its remote telemetry sources are reachable. Pulse provides read-only operational evidence: perform infrastructure changes through the appropriate operator workflow.
+
 ## Production deployment
 
 Begin with the [public deployment guide](docs/PUBLIC_DEPLOYMENT.md). A production instance needs HTTPS, Authentik/OIDC, private PostgreSQL, externally managed secrets, a defined Prometheus source, least-privilege Unraid API access where required, a backup directory, and a reviewed network and mount projection. The supplied configuration fails closed when mandatory production settings are absent. Validate backup, restore and rollback before relying on alerts.