VERIFYFIRST // process-list
What is running — You checked ps, pgrep, or systemctl status.

WHAT IT CAPTURES
  That a process with a matching name exists and has a state.

WHAT IT CANNOT SEE
  - Whether the running process corresponds to the code currently on disk.
  - Your own command, which matches the pattern you are searching for.
  - Whether the environment you are inspecting is the one you are running inside.

KNOWN FAILURES (3)

  NS-012  A pattern search for a process matches the search itself
    reads as   pgrep -f chromium returns a match after cleanup. Conclusion drawn: an instance is still running.
    actually   The pattern appears in the command line of the pgrep invocation, so the search finds itself. Nothing is running.
    check      Resolve the PID and compare it against your own: pgrep -f PATTERN | grep -v "^$$\$", or list full command lines with pgrep -af and read them.

  NS-026  systemd reports a Type=simple unit active before the service binary has been executed
    reads as   `systemctl start app` returns and `systemctl is-active app` says active. Conclusion drawn: the service is up and accepting connections.
    actually   For Type=simple the service manager considers the unit started immediately after the main service process has been forked off — after fork() and before the new process has called execve() to invoke the actual service binary. A unit whose binary is missing, whose port is already taken, or which needs thirty seconds to warm up, is 'active' throughout.
    check      Ask the socket rather than the manager: `ss -ltnp 'sport = :8000'` returns a listener only when one exists, and is empty while the unit is active but not yet serving. A single request to the port distinguishes the same two states.

  NS-027  A service crash-looping every few seconds reads as active between crashes
    reads as   `systemctl status app` shows active (running) with a PID. Conclusion drawn: the service is healthy.
    actually   With Restart=always the unit crashes, waits RestartSec, and starts again. Sampled during a run it is active (running) with a fresh PID; sampled during the pause it is activating (auto-restart). Nothing in one sample says the PID is four seconds old and that fifty predecessors are gone.
    check      Read the restart counter and the start timestamp twice, thirty seconds apart: `systemctl show -p NRestarts -p ExecMainStartTimestamp --value app`. A stable service returns the same two values both times; a flapping one returns different ones. Both properties are exposed by systemd for every service unit.

---
Full registry: https://verifyfirst.dev/registry.json
This page:     https://verifyfirst.dev/process-list/
CC0-1.0. Every entry observed, none hypothetical.