AI & RAG

Weekly ADR Supersession and Staleness Audit

Scans all Architecture Decision Records on a schedule, finds ones that reference superseded decisions or contradict newer ADRs, and posts a triage digest to Slack with cited fixes.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionPull all ADRs with status and links from ConfluenceConfluenceConfluence
  • LogicBuild supersession graph, find dangling refs and contradictions
  • ActionSummarize issues with ADR numbers and fixesOpenAI
  • OutputPost prioritized triage digest to SlackSlack

What it does

Keeps your ADR library internally consistent. On a weekly schedule it reads every Architecture Decision Record, builds a map of which decisions supersede which, and flags problems: accepted ADRs that still cite a now-superseded one, decisions that contradict a newer ADR, and records that have gone stale. It outputs a ranked triage list so a maintainer can clean up in minutes.

When to use it

When your ADR collection has grown past the point any one person tracks it, and supersession links rot. Run it for architecture leads who own decision hygiene but can't reread the whole corpus.

How it works

  1. 1A weekly schedule fires the audit.
  2. 2All ADRs are pulled from Confluence with their status and supersedes/superseded-by fields.
  3. 3A logic step builds the supersession graph and finds dangling references and contradictions.
  4. 4OpenAI summarizes each issue with the ADR numbers involved and a suggested resolution.
  5. 5A prioritized digest is posted to the architecture channel in Slack for triage.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ConfluenceSpaces, pages, blueprints.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.