Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaDroidsProcess Registration AuditorMain page

Process Registration Auditor

Droid scan caroladmin crontab + carol-* systemd units; cross-reference the droids registry; write unregistered processes to themis.db findings
Go to droid →

📖About & Usage

About

The Process Registration Auditor is a weekly integrity check that hunts down any process running in Carol’s infrastructure without being registered as a droid. Its job is to stop “ghost” processes from slipping past governance — if something triggers on the VM, it must have an owner and a purpose. Findings go straight into the audit database so Themis can flag them in the Themis Monitor weekly report.

Every Sunday at 06:10, the droid scans the caroladmin crontab and all systemd units labelled `carol-*`, then cross‑references every active or scheduled process against the official droids registry. Any process that isn’t found there gets recorded as an unregistered entry in the themis.db findings table. It never changes anything — it’s a pure read‑only observer, so it can’t break the system while it’s auditing.

Its owner is Themis, who relies on the results to maintain a clean process landscape. This droid is a one‑of‑a‑kind tool, not part of a shared family; it falls into the catch‑all “(none)” family, which currently counts 212 such unique droids across the Carolverse. Because its execution engine hasn’t been recorded yet, we don’t know whether it runs as a straight software script or calls Claude — for now, its engine remains a mystery.

👤Owner

Themis · Head of Legal & Compliance

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.

No initiatives recorded for this droid yet.