Conductor

The Conductor is the always-on layer of the swarm: instead of waiting for a prompt, it watches your connected estate — documentation drift, reversible hygiene, quality baselines, cost anomalies — and compiles standing goals (“tables in analytics stay documented”) into routine work for the fleet.

The two modes

You choose how much initiative it gets, and you can switch anytime:

Approve-edits — the Conductor proposes every change; you click approve. Start here, watch it for a day, then flip to Auto in one click. No penalty, no re-onboarding.
Auto — it performs reversible upkeep itself and tells you after; stop or undo anytime.

The floor that never moves

Regardless of mode: reversible means you can undo it — a description, a tag, a re-run. Irreversible means you can’t — a delete, an access grant, anything that spends money. Irreversible actions always ask first, in every mode, with the exact change and blast radius shown. Even with no zones configured, the Conductor can never spend, change access, or delete without asking.

Everything it does lands in the same receipt-and-audit trail as any governed write, and its track record — changes made, kept, undone — is visible, so trust is earned from your own history rather than asserted.

Where it runs

Hosted by us as part of your workspace on every plan — inside your own deployment boundary on Enterprise dedicated/on-prem. Enabling it and choosing its mode is part of pilot onboarding. Self-hosting the Conductor on your own infrastructure is also supported for teams that require it — raise it with your onboarding engineer.