AI AGENTS

Weekly refresh of open strategic questions into a Confluence dossier

On a weekly schedule, reads a list of open strategic questions, re-researches each one for new evidence.

CategoryAI Agents
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRead open questions from Confluence dossierConfluenceConfluence
  • ActionRe-research each question's sub-queriesExa
  • ActionDiff new findings vs last week's answerOpenAI
  • LogicRoute changed vs unchanged questions
  • OutputUpdate Confluence dossier with changelogConfluenceConfluence

What it does

Keeps a set of standing strategic questions continuously researched. Each week the agent re-runs research on every open question, compares against the prior answer, and updates a Confluence dossier so leadership always sees a current, sourced view with a changelog.

When to use it

When you track recurring decisions, like pricing posture, competitor moves, or regulatory shifts, that need watching rather than a one-time answer. Replaces the stale quarterly deck with a living document.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2The agent pulls the list of open questions from the existing Confluence dossier.
  3. 3For each question it decomposes into sub-queries and runs fresh web research.
  4. 4An LLM step diffs new findings against last week's recorded answer.
  5. 5A logic step routes: unchanged questions get a "no change" stamp; changed ones get a rewritten section plus a "what changed" callout.
  6. 6The dossier is updated in place with refreshed citations and dated revision notes.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ConfluenceSpaces, pages, blueprints.
  2. 2
    Connect ExaNeural search across the web.
  3. 3
    Connect OpenAIModels, embeddings, 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.