AI & RAG

Weekly Runbook Citation Link-Rot and Drift Audit

Runs weekly to verify every cited runbook section still exists at its anchor and version in Confluence, flags drifted or deleted citations, and posts a remediation report to Slack.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires the audit run
  • ActionLoad all distinct cited page IDs and anchors from PostgresPostgreSQLPostgres
  • ActionFetch each live Confluence page and compare anchor and versionConfluenceConfluence
  • LogicClassify each citation as healthy, drifted, or broken
  • OutputPost a remediation report of broken and drifted citations to SlackSlack

What it does

Audits the integrity of your grounded-answer pipeline. On a schedule it walks every section the index claims to cite, checks the live Confluence page for that heading anchor and version, and detects three failure modes: the page was deleted, the heading anchor moved or was renamed, or the content changed enough that the stored embedding is stale.

When to use it

Use it when you depend on citation links staying valid and want to catch silent link rot before an engineer clicks a dead 'Source' link mid-incident.

How it works

  1. 1A weekly schedule starts the audit.
  2. 2The flow loads all distinct cited page IDs and anchors from Postgres.
  3. 3For each, it fetches the current Confluence page and compares anchor presence and version hash.
  4. 4A branch classifies each citation as healthy, drifted, or broken.
  5. 5A summary with counts and a per-item table of broken and drifted citations is posted to the platform team's Slack channel for remediation.

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 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.