AI & RAG

ADR Weekly Digest: summarize new and superseded decisions to Teams

Each week, gathers ADRs that were added, accepted, or superseded, summarizes the architectural impact with an LLM.

CategoryAI & RAG
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly digest schedule fires
  • ActionQuery Postgres for ADRs changed this weekPostgreSQLPostgres
  • ActionFetch current ADR bodies from ConfluenceConfluenceConfluence
  • ActionSummarize decision changes with OpenAIOpenAI
  • OutputPost digest to Microsoft Teams channelMicrosoft Teams

What it does

Produces a weekly architecture decision digest. It looks at which ADRs changed status in the last seven days, explains in plain language what was decided and what it supersedes, and broadcasts a concise summary to a Microsoft Teams channel.

When to use it

Use it when decisions get made but never communicated, when distributed teams miss that a standard changed, or when leadership wants a lightweight pulse on architecture direction without reading every ADR.

How it works

  1. 1A weekly schedule triggers the digest.
  2. 2The flow queries Postgres for ADRs whose status or version changed in the trailing week.
  3. 3It fetches the current bodies of those ADRs from Confluence.
  4. 4OpenAI writes a grouped summary (new, accepted, superseded, deprecated) with one-line rationale and links.
  5. 5The formatted digest posts to the designated Microsoft Teams channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect Microsoft TeamsChannels, chats, files.
  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.