AI & RAG

Agent That Answers Complex Policy Questions Across Multiple Contracts

An agent that decomposes a multi-part contract question, retrieves and reconciles clauses across several versioned policy and contract sources.

CategoryAI & RAG
Enginepaperclip
Difficultyadvanced
Triggerchat
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerUser submits a complex multi-part question via chat
  • LogicDecompose into sub-questions and plan retrieval
  • ActionRetrieve grounded chunks from Supabase per sub-questionSupabaseSupabase
  • ActionFetch authoritative page text and versions from ConfluenceConfluenceConfluence
  • ActionReconcile versions and synthesize cited answer with OpenAIOpenAI
  • OutputSave fully cited synthesis to Notion and return to userNotionNotion

What it does

Handles questions that no single paragraph can answer, such as "How does our standard indemnity differ from the enterprise template, and which version introduced the change?" The agent plans sub-queries, pulls grounded evidence from your Confluence policy library and a Supabase vector index, reconciles conflicts across versions, and writes a structured answer where every claim links to its source paragraph and revision.

When to use it

Use it for cross-document, comparative, or historical policy questions that need reasoning over multiple sources rather than a single lookup. Suited to legal and deal-desk teams who need defensible, fully cited synthesis saved for the record.

How it works

  1. 1A user submits a complex question through a chat trigger.
  2. 2The agent decomposes it into sub-questions and plans retrieval steps.
  3. 3For each sub-question it retrieves grounded chunks from Supabase and fetches authoritative page text from Confluence.
  4. 4The agent reconciles version differences and assembles a cited synthesis with OpenAI.
  5. 5The final answer, with per-claim citations and versions, is saved to a Notion page and returned to the user.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SupabaseTables, auth, storage, edge functions.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect NotionPages, databases, comments.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.