About 5 months ago, I shared the early stages of Titan, a lightweight distributed orchestrator built entirely from scratch in Java 17. The strict design constraint was zero external dependencies by using only java.net.Socket and java.util.concurrent (no Spring, no Netty). The entire engine had to run from a single JAR. Since then, the project has grown into a highly concurrent distributed execution runtime. Before diving in this is the base comparison I want to put forward to avoid confusion Titan is a zero-dependency distributed execution runtime. It assumes your compute infrastructure already exists, and acts as the application layer on top of it by coordinating dynamic DAGs, managing long-running detached processes, and sharing cross-node state without requiring an external database. Is it like Kubernetes? No. Kubernetes provisions virtual networks and orchestrates Docker containers. Titan doesn't know what a container is; it orchestrates host-level processes. ​Is it like Terraform/Ansible? No.…