Concepts

• Listener vs proactive workers — Listener workers wait for external events and are fully implemented; proactive workers run on schedules and are typed but not executed yet in v0.1.
• Pause vs stop — Pause suspends work while the process keeps running; stop exits the process entirely.
• Service discovery via package.json — Servix finds a service entry through the servix.entry field in package.json, so any compatible npm package is installable by name.
• The service shell — Servix is the lifecycle shell around your logic — it supervises, schedules, logs, and persists, but never becomes the business logic.
• Wrap once, run managed — You wrap existing logic exactly once with defineServixService; from then on it behaves like an installable, controllable service.