AI & RAG

Policy conflict and contradiction detector

On a schedule, scans your Confluence and Drive policy library for statements that contradict each other (e.g. two different PTO rules) and posts a triage report to Slack so doc…

CategoryAI & RAG
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionCluster related policy chunks from SupabaseSupabaseSupabase
  • ActionJudge contradictions across passages (OpenAI)OpenAI
  • LogicKeep only confirmed, high-severity conflicts
  • OutputPost triage report with source links to SlackSlack

What it does

Finds where your own policies disagree. It clusters semantically related passages across Confluence and Drive, asks the model to judge whether any pair genuinely conflicts, and reports the contradictions with both source links so an owner can fix the canonical version.

When to use it

Use it when policy lives in many places and has drifted over time, before an audit, or after a big reorg. It is the cleanup companion to a Q&A bot: a bot can only be trustworthy if the underlying docs do not contradict each other.

How it works

  1. 1A scheduled trigger starts the scan (e.g. weekly).
  2. 2The workflow pulls policy chunks from the Supabase vector store and clusters near-duplicate topics.
  3. 3OpenAI evaluates each candidate cluster and labels real contradictions, ignoring harmless restatements.
  4. 4A filter keeps only confirmed conflicts above a severity bar.
  5. 5A formatted triage report with both conflicting passages and links is posted to a Slack channel for doc owners.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SupabaseTables, auth, storage, edge functions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  4. 4
    Connect Google DriveDocs, sheets, slides, files.
  5. 5
    Connect SlackChannels, DMs, threads, mentions.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.