Glossary

Pill

A pill is Glitch Team Zone's word for a runnable tool: a prompt bundled with a behavior that a department owns. A pill can be run from chat on demand or set to run on a schedule, and every run keeps a record of what it did, what it cost, and whether it needed a human to step in. It's the unit of automation in the product, the thing a team runs instead of writing and maintaining a one-off script.

Departments end up with a long list of small, repeatable jobs: check for a spend threshold, draft a weekly summary, look for gaps in support responses. Each one is too small to justify custom software and too easy to forget if it lives only in someone's head. A pill is the middle ground: defined once, run as many times as needed, owned by the department instead of a central engineering team.

In Glitch Team Zone, every pill run shows its cost and outcome, so a department can see what automation is actually spending instead of guessing. Run details also feed the conductor's findings and a default-on telemetry stream that helps the next version of a pill start smarter than the last one, which any admin can see in full and switch off.

A pill can be as small as a spend check that posts to a channel the moment a number crosses a line, or as involved as the kind that reads a department for a recurring, removable problem and proposes one concrete move to fix it. What they share is the shape: a defined job, a place it reports to, and a cost a team can see.