AI & RAG

Flag non-standard clauses against your playbook on every new version

When a new contract version is indexed, it checks key clauses against your approved fallback playbook and, if any deviate, posts an alert with the offending clause.

CategoryAI & RAG
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew contract version indexed
  • ActionRetrieve playbook-relevant clausesSupabaseSupabase
  • ActionEvaluate clauses against playbook standardsOpenAI
  • LogicExit if all clauses within approved bounds
  • OutputPost deviation alert to Microsoft TeamsMicrosoft Teams

What it does

Acts as an automated first-pass reviewer. As soon as a contract version enters the clause store, it retrieves the clauses that matter — liability caps, indemnity, governing law, auto-renewal — and compares each to your negotiation playbook. Anything outside approved bounds gets surfaced immediately with the exact clause text and the standard position it violates.

When to use it

When contract volume outpaces legal's ability to read every draft, but off-playbook terms create real risk. This catches the deviations worth a human's attention and lets the rest pass quietly.

How it works

  1. 1A new indexed version emits an event trigger.
  2. 2Supabase returns the playbook-relevant clauses for that version.
  3. 3OpenAI evaluates each clause against the stored standard positions and flags deviations.
  4. 4A logic step exits silently if every clause is within bounds.
  5. 5For any deviation, an alert is posted to Microsoft Teams with the clause, the standard, and a citation linking the source version.

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 Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.