AI & RAG

Runbook Staleness Auditor with Drive and Confluence Cross-Checks

Weekly job that uses the runbook agent to flag procedures contradicted by newer docs, missing owners, or unreferenced for months, and files the findings as Linear issues.

CategoryAI & RAG
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly scheduled audit run
  • ActionPull procedure batch and fetch live source versionsConfluenceConfluence
  • ActionDetect contradictions and stale references with citationsOpenAI
  • LogicKeep only findings above severity threshold
  • OutputFile each finding as a Linear issue to the doc ownerLinearLinear

What it does

Proactively audits your runbook corpus for rot. It samples indexed Confluence and Drive procedures, asks the agent to detect internal contradictions, outdated tool names, and orphaned ownership, and cross-checks claims against the live source. Each problem becomes a Linear issue assigned to the doc owner with the offending citation included.

When to use it

Use it when your knowledge base has grown faster than anyone can maintain and answer quality is slipping because the agent grounds replies in stale pages. Running it weekly keeps the corpus trustworthy for every downstream answer flow.

How it works

  1. 1A scheduled weekly trigger starts the audit.
  2. 2The flow pulls a batch of indexed procedures from Postgres and fetches their current Confluence and Drive versions.
  3. 3OpenAI evaluates each procedure for contradictions, dead references, and missing owners, citing exact passages.
  4. 4A logic step keeps only items above a severity threshold.
  5. 5Each flagged finding is filed as a Linear issue tagged with the source link and suggested fix.

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 Google DriveDocs, sheets, slides, files.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Connect LinearIssues, projects, cycles, triage.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    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.