A Forge app for Confluence, built for Codegeist 2026

Docs that know when the code moved.

Doc Drift anchors Confluence pages to code and Jira work, flags them when those change, and tells Rovo and coding agents which pages to trust.

  • No AI in detection
  • Agents never edit pages
  • Respects page permissions
Verified by Dana, 3 days ago
PlatformRunbooks

Payments rollback runbook

Roll back a release

  1. Page the payments on-call engineer and post in the incident channel.
  2. From the repo root, run scripts/rollback.sh with the release tag.
  3. Wait for ROLLBACK_TIMEOUT to pass, then check the error rate.

check-page-freshness
{
  "title": "Payments rollback runbook",
  "status": "verified",
  "guidance": "Safe to cite."
}

The problem

Docs rot when systems change, not when calendars turn.

“What actually invalidates technical docs isn't time passing, it's the system changing underneath them. How-tos, process docs, configuration guides: these are the dangerous ones.”

A member of the Atlassian Community

Review dates miss it

A page untouched for 2 years can be correct. A page reviewed last month can be out of date after one merge. Page age and review reminders can't tell the two apart.

Agents can't tell either

Rovo and coding agents read the same pages and cite them with confidence. Nothing tells them that the script in step 2 was renamed last week.

The cost lands at 3am

The on-call engineer follows the runbook, and the command it names no longer exists. A runbook that's out of date can be worse than none.

How it works

Catch the slip.

Anchor a page to what it describes. When that moves, the page says so, and agents hold off until someone has looked.

01

In sync

The rollback runbook is anchored to scripts/rollback.sh in payments-api, and to the PAY-142 epic. Someone checked it against both.

Verified
02

Code moved

PR #482 merges and renames the script. A deterministic matcher scores the change against every anchor. The page badge turns Possibly stale, the owner gets a comment, and agents are told to caveat.

Possibly stale
03

Reviewed

Dana opens the review panel, sees the rename and the step it affects, and accepts the fix. The page is Verified again, and agents trust it again.

Verified

Inside Confluence

Everything happens on the page.

No new tool to check. The badge sits in the page byline, and one click opens what changed and what to do about it.

See exactly what changed

The review panel names the pull request or Jira change, who made it, the files, and why it flagged this page. Then you decide: mark it verified, snooze it, dismiss it with a reason, or fix it.

PR #482merged by Sam · 2 hours ago High
PR #482 renamed a script that step 2 runs.
scripts/rollback.sh → scripts/rollback-v2.sh
PAY-142moved to Done · Yesterday Medium
The epic this page is anchored to was closed.

A badge in the byline

Four states, always a word and an icon. The state is stored with the page, so the badge loads with it and page views run no app code.

VerifiedChecked since its anchors changed
Possibly staleAn anchor changed
StaleUnreviewed for 7 days, or 3 changes
UnanchoredNot linked yet

Anchors from the page itself

Doc Drift reads the paths, repo links and Jira keys already on the page and suggests them. Tick, save, done. Or anchor a whole space at once.

  • payments-api: scripts/rollback.sh
  • payments-api: deploy/helm/**
  • PAY-142
  • payments-api (whole repo)

Fixes you approve

Drift Reviewer drafts new text for the affected step. For a plain rename, Doc Drift proposes the swap itself, with no AI. Nothing changes until you accept.

- run scripts/rollback.sh <tag>
+ run scripts/rollback-v2.sh <tag>

Suggested from PR #482. Saved as a new page version, by you.

Drift debt per space

A dashboard in each space ranks the pages that need a look and groups them by owner, so a team can clear them in one sitting.

18 of 24Pages anchored
5Possibly stale

Sample data from the demo space.

Track the update in Jira

Not fixing it today? Create a Jira task from the panel. It lists the changes and the sections to re-read, and agents see that an update is tracked.

Update “Payments rollback runbook”: anchors changed in PR #482PAY-201

Closing the task doesn't mark the page Verified. A person still checks the page.

The owner hears about it

A short comment on the page mentions the owner, names the change and links to the review. Changes that land together become one comment.

Doc Driftcommented
@Dana PR #482 (merged by Sam) changed 2 files this page documents. Review in the Doc Drift badge.
  • Tuned by your adminSensitivity presets, ignored paths, watched spaces, escalation days and comment timing.
  • Reverts close driftWhen a pull request is reverted, the drift it caused closes on its own.
  • Follows renamesA moved file is matched to its old path, so the anchor still fires.
  • Learns from dismissalsDismiss a change as not relevant, and you can stop watching that path for the page.
  • Demo modeReplay a seeded pull request from settings to see the whole flow without Bitbucket.
  • Jira anchors tooStatus, fix version, scope and parent changes on anchored issues flag the page.

For agents

Agents check before they cite.

The same freshness signal people see in the byline is a tool any agent can call: the Drift Reviewer agent in Rovo, and coding agents like Claude Code and Cursor over MCP.

Claude Code · find-docs-for-path
> Before I edit deploy/helm/values.yaml, which docs describe it?

doc-drift · find-docs-for-path (repo: "payments-api", path: "deploy/helm/values.yaml")
  5 pages
  Payments API service overview        possibly_stale  exact
  Scale payment workers                possibly_stale  exact
  Fail over the payments database      verified        exact
  Payments rollback runbook            verified        exact
  Payments deployment and Helm chart   verified        glob deploy/helm/**

5 pages document this file, and 2 are already Possibly stale. I'll make the change, then list all 5 in the pull request so their owners can re-check them.
Output from the demo space.

Connect a coding agent

One MCP server per site. Agents read as the person who signs in, so they only see pages that person can view.

  1. An admin turns on the tools

    In Atlassian Administration: Apps, Sites, your site, Connected apps, Doc Drift, then Tools.

  2. Open the app once in Confluence

    Click any Doc Drift badge and allow access. Agents act as you, so this consent comes first.

  3. Add the server and sign in

    In Claude Code, run this, then /mcp to sign in.

    claude mcp add --transport http doc-drift https://mcp.atlassian.com/forge/12e968a1-a45d-4524-ba28-d47e2315db1a
Cursor and other MCP clients Server URL
https://mcp.atlassian.com/forge/12e968a1-a45d-4524-ba28-d47e2315db1a
Cursor, in .cursor/mcp.json
{ "mcpServers": { "doc-drift": { "url": "https://mcp.atlassian.com/forge/12e968a1-a45d-4524-ba28-d47e2315db1a" } } }

Tell your agent the rule

Paste this into CLAUDE.md or AGENTS.md. Your agent then checks a page before it relies on it, and trusts the code when the two disagree.

Before you rely on a Confluence page, call the `check-page-freshness` tool from the doc-drift MCP server with its page ID or URL. If the state is not `verified`, do not present its steps as current, and tell the user which page needs a review. When a page and the code disagree, trust the code.
What agents can and can't do
  • Read page states, open changes and the pages that cover a file
  • Draft a fix for a person to accept (Drift Reviewer only)
  • Never edit a page, and never see a page the person can't view

Built to be trusted

A person decides.

Doc Drift watches and flags. It never claims a page is wrong, only that what it describes has changed.

No AI in detection

A deterministic matcher scores each change against anchors: paths, globs, renames, removed identifiers. Same input, same result, no credits spent.

Agents never edit pages

Page text changes only when a person clicks Accept, as that person, with a version message naming the pull request. Page history can undo it.

Permission-aware

Agents and tools read as the signed-in person. A page they can't view comes back as unknown, with no title.

No page bodies stored

Doc Drift keeps anchors, scores, pull request details and file paths. Diff text is deleted after 30 days. A fix draft keeps only the block it replaces.

Signed changes, no servers of ours

Both apps run on Atlassian Forge. The Bitbucket relay signs each change with a secret unique to your site, and talks only to the Confluence app.

AI only when you ask

Drafting a fix runs in Rovo on your site, only after someone clicks Propose fix. It sees the affected sections and the change, not your repository.

Read how Doc Drift handles data

Get started

Three steps to your first flag.

  1. 01

    Install in Confluence

    A site admin installs Doc Drift. Jira is optional: connect it to watch issues too.

  2. 02

    Connect Bitbucket

    Install the relay in your Bitbucket workspace and paste the URL and secret from settings. Or skip this for now and replay the demo pull request.

  3. 03

    Anchor your pages

    Click the badge on a runbook and accept the suggested anchors. The next merge that touches them flags the page.

Install for Confluence Read the setup guide The install link is shared with Codegeist 2026 judges first.

Questions

Good to know.

Does it use AI to decide a page is stale?

No. Detection is a deterministic matcher: it compares the files and identifiers a change touched with the anchors on each page. AI runs only when someone clicks Propose fix, and a person still accepts the result.

Which code hosts does it support?

Bitbucket Cloud, through a small relay app in a team workspace. GitHub and GitLab are not supported yet. Jira issues can be anchors on their own, so a page can be watched with no code host at all.

Do I need Rovo?

No. The badge, review panel, dashboard, comments, Jira tasks and the rename quick fix work without it. The Drift Reviewer agent and Propose fix need Rovo on your site, and drafting a fix uses Rovo credits there.

Will it edit my pages?

Only when you accept a proposed fix. The edit is saved as a new page version under your name, with a message that names the pull request, so page history can undo it. The app writes its badge to page metadata, never to the page text.

What about pages with view restrictions?

They can't be watched yet. The app can't read them, so it says so in the badge and tells agents to check those pages against the code before citing them.

How much does it cost?

Doc Drift is free while it's in preview. Drafting fixes with Drift Reviewer uses Rovo credits on your own site.

Catch the slip before your agents do.

Docs that agents can trust, because they know when to stop trusting them.