AI & RAG

Weekly Stale-RFC Digest From Code-Doc Drift

Weekly, cross-references Confluence RFCs against the current GitHub code they describe, flags RFCs whose implementation has diverged.

CategoryAI & RAG
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRetrieve current GitHub code per RFCGitHubGitHub
  • ActionCompare doc vs code, score driftOpenAI
  • LogicFilter and rank RFCs over drift threshold
  • OutputEmail leads the stale-RFC digestGmailGmail

What it does

Surfaces documentation rot before it misleads anyone. Each week it walks your indexed RFCs, pulls the GitHub code each one references, and uses retrieval plus comparison to detect where the implementation no longer matches the documented design. It ranks the mismatches and sends engineering leads a single digest of the most-diverged RFCs with links to both sides.

When to use it

When RFCs are written once and rarely updated while code keeps moving, leaving an answer-bot grounded in outdated truth. Run alongside the index builder.

How it works

  1. 1A weekly schedule fires the audit.
  2. 2The flow iterates RFC entries and retrieves the matching current GitHub source for each.
  3. 3OpenAI compares documented design against actual code and assigns a drift score with cited evidence.
  4. 4A logic step filters to RFCs exceeding the drift threshold and sorts by severity.
  5. 5The flow emails engineering leads a ranked digest, each entry linking the RFC page and the diverged code.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ConfluenceSpaces, pages, blueprints.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect GmailRead, draft, send, label.
  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.