What happens to your agent's memory when a daemon dies at 2am?
Your memory stack runs on local daemons, and when one dies quietly overnight you pay the next morning: a session that forgot everything and twenty minutes re-explaining a codebase your agent knew yesterday. Doctor watches the whole stack, heals what breaks, and has your memory back before your next prompt, usually without you noticing.
curl -fsSL https://get.theapiary.sh | sh A daemon crashed. Do I have to fix it?
No. Doctor probes every service every 30 seconds and climbs a repair ladder: restart, reinstall after repeated fails, remove a conflicting package, back off, and stop the instant health returns. Kill one on purpose and it is typically back within one probe.
Will it nag me?
No. A healthy check is a single debug line, so Doctor stays silent on the happy path. It only speaks up when the ladder runs out, and then it writes a plain do-this-next report on a local status page.
Could an auto-update brick my setup?
No. Doctor updates the memory daemon only behind a blessed-release gate, verifies health afterward, and rolls a bad update back automatically. A broken release cannot spread itself to your machine.
Can it touch my credentials?
Never. Doctor has no code that can read or delete your credentials file. If it suspects a credential problem it tells you and stops, full stop.
What does a silent memory outage cost you across a whole team?
Your engineers' memory runs on local daemons, and a daemon that dies quietly costs every developer it touches: forgotten sessions and time re-explaining code the agent already knew. Doctor is the watchdog that stands outside every failure it watches, heals the stack automatically, and keeps it current safely, so the outage and the fix both happen without a ticket.
Who fixes the stack when it breaks?
Doctor does, on its own. It probes every daemon every 30 seconds, diagnoses the kind of failure, and repairs it on a backoff ladder, escalating with a structured report only when it genuinely cannot. Your team stays in flow instead of filing tickets.
How do we roll out updates without breaking machines?
Doctor auto-updates only behind a blessed-release gate: a version must be explicitly approved, the update is verified healthy, and a failed verify rolls back on its own. One bad release cannot spread across your fleet.
Is it a security liability?
No. Doctor is zero-dependency, runs per-user with no admin rights, and has no code that can read or delete credentials. Its escalation reports land on a local status page first and never carry your code or secrets.
How much operational overhead does it add?
Almost none. It is deliberately boring: silent when healthy, supervised by the OS so it survives reboots, and harder to kill than what it watches. The whole point is that nobody has to think about it.
