I have noticed that in the technology world (speaking of data in particular) there is a disconnect between the product side and customers running software. For the most part companies building product focus on build and deployment. Which is only natural as that is what the devs are constantly doing. They need to spin up instances to add new feature, test bugs, and work with integrations. In order to save money, rapid deployment and limiting the amount of uptime tends to lead the thought process. Conversely on the customer side the instances are commonly running for months if not years. In some cases it is the instances/hosts that run the machines, but if not the expectation is that those can be swapped out and the service maintains uptime throughout. In this case downtime is a cost versus a benefit. So it is two opposite worlds. I can look at this tension and see it in the broader world. People are very eager to build and get something new, there is a natural bend to discovery that is part of the human condition. In general we are very poor at maintenance and improvement of what we have.
Extensible Gemini/Titan server
When something is running on a system (whether it is a process, a service, or something bound to a port) there is always a cause. That cause is often indirect, non-obvious, or spread across multiple layers such as supervisors, containers, services, or shells.
Existing tools (ps, top, lsof, ss, systemctl, docker ps) expose state and metadata. They show what is running, but leave the user to infer why by manually correlating outputs across tools.
witr makes that causality explicit.
It explains where a running thing came from, how it was started, and what chain of systems is responsible for it existing right now, in a single, human-readable output.