Agent #009 · RevOps
Pipeline Hygiene Agent: governance & failure modes
What this agent is built not to do, and the specific ways it can fail if misconfigured.
Governance notes
- This agent only recommends — it has no CRM write permission for stage, amount, or close-date fields, only for its own agent-owned flag and score fields.
- Closing or re-staging a deal is always a human action; the agent’s job ends at a specific, actionable flag.
- Stage-age thresholds are set per stage in config, since normal time in Discovery and normal time in Negotiation are very different numbers.
- The champion check degrades gracefully when the Buying Committee Mapper isn’t deployed — it’s disabled in config rather than always failing.
Failure modes
- Agent accidentally closes or re-stages a deal: prevented structurally — write credentials are scoped only to agent-owned fields, and a QA test asserts no write attempt ever reaches stage, amount, or close-date fields.
- Vague next steps not caught: the vague-phrase pattern list is versioned and expanded every time a miss gets caught in review.
- Stage-age threshold flags normal early-stage deals: prevented by requiring a threshold per stage in config rather than one global number.
- Forecast-inconsistency check never fires: a deliberately inconsistent test deal (Commit category, 90-day-out close date) is part of QA specifically to verify this check actually catches what it’s supposed to.