How it works
Tritt evaluates an execution request, maps affected projects and dependencies, and routes work to the appropriate Paseo workspaces. Independent tasks run in parallel by default; only real dependencies, mutable-state conflicts, or shared-resource limits serialize the affected work.
The current v0 is a documented, dogfooded orchestration contract rather than a standalone service. Paseo remains the execution runtime, Baton coordinates desktop-sensitive work, mētis supplies project policy, and Nopi observes runtime state. Tritt does not yet include its own scheduler, database, desktop UI, or agent runtime.
Next
Use the foundation across real multi-project work and refine the contract from evidence. A dedicated implementation should follow only where native Paseo orchestration no longer covers a demonstrated need.