📖About & Usage

About

The Policy Conflict Checker is a droid owned by Orion that keeps Carol’s policies from tripping over each other. Every time a new policy candidate is proposed, this droid automatically compares it against every active policy already on the books. If it spots a conflict—whether a direct contradiction, an overlapping scope, or a candidate that would supersede an existing rule—it flags the problem, explains why, and points to the exact policy IDs involved. The flagged results are then written back onto the candidate so the Proposed queue can clearly highlight any issues before anyone approves the change.

Under the hood, the droid uses a large language model to do the heavy lifting: it retrieves related active policies for a given candidate and asks the LLM to classify the type of conflict, generate a human-readable explanation, and cite the specific policy IDs that are in tension. Because it’s triggered on new submissions, it acts like a safety catch, preventing inconsistent rules from sneaking into Carol’s policy framework. It can also be run manually against any candidate that hasn’t been checked yet, making it handy for one-off reviews.

This is a bespoke, one‑off tool built just for Orion—it’s not part of a reusable droid family that other agents share. While the registry lists 213 droids across the Carolverse in the “(none)” category (meaning they’re all custom, stand‑alone workers), each has a unique name and purpose. Curiously, its exact execution engine isn’t documented yet; it definitely calls an LLM to do the analysis, but whether that’s software-based or Claude isn’t recorded, so the engine field remains unknown.

👤Owner

📚Recent initiatives

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

No initiatives recorded for this droid yet.