Concept
Wrap once, run managed
You wrap existing logic exactly once with defineServixService; from then on it behaves like an installable, controllable service.
Problem
Rewriting working logic into bespoke daemons duplicates effort and loses the original package's reusability.
Mental model
Take anything useful, wrap it once, then run it like a service.
The output of wrapping is not just "some code" — it becomes an installable npm package:
Existing logic → Servix wrapper → New npm package → npm install -g … → servix start/stop/pause/status/logs
Servix can wrap a TypeScript function, an existing npm package, a CLI command, a long-running listener, a scheduled job, or an API polling worker.