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.
A Forge app for Confluence, built for Codegeist 2026
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.
Payments rollback runbook
Roll back a release
scripts/rollback.sh with the release tag.ROLLBACK_TIMEOUT to pass, then check the error rate.{
"title": "Payments rollback runbook",
"status": "verified",
"guidance": "Safe to cite."
}
The problem
“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 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.
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 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
Anchor a page to what it describes. When that moves, the page says so, and agents hold off until someone has looked.
The rollback runbook is anchored to scripts/rollback.sh in payments-api, and to the PAY-142 epic. Someone checked it against both.
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 staleDana 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.
VerifiedInside Confluence
No new tool to check. The badge sits in the page byline, and one click opens what changed and what to do about it.
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.
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.
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.
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.
Suggested from PR #482. Saved as a new page version, by you.
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.
Sample data from the demo space.
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.
Closing the task doesn't mark the page Verified. A person still checks the page.
A short comment on the page mentions the owner, names the change and links to the review. Changes that land together become one comment.
For agents
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.
> 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.
> How do I roll back payments-api? Check the runbook first. doc-drift · check-page-freshness (pageUrl: ".../Payments+rollback+runbook") { "title": "Payments rollback runbook", "status": "possibly_stale", "citePolicy": "cite_with_caveat", "openDrift": [{ "ref": "PR #482", "summary": "renamed scripts/rollback.sh to scripts/rollback-v2.sh", "severity": "high" }], "guidance": "Do not present steps from this page as current. Cite with caveat: what it describes changed in PR #482 on 2026-11-10, after it was last verified." } The runbook may be out of date: PR #482 renamed the rollback script after the page was last verified. In the code, the script is now scripts/rollback-v2.sh. Example after the demo replay of PR #482.
> Which PLAT pages should I review this week? doc-drift · list-stale-pages (spaceKey: "PLAT", limit: 5) Scale payment workers possibly_stale high PR #5 Refunds API guide possibly_stale high PR #12 Payments codebase tour possibly_stale high PR #13 Payments local development setup possibly_stale high PR #13 Payments API service overview possibly_stale medium 2 changes 5 PLAT pages have open changes, 4 of them high. Start with the Refunds API guide: PR #12 removed src/routes/refunds-v1.ts, which the guide documents. Output from the demo space.
scripts/rollback.sh after the page was last verified, so step 2 may be out of date. Want me to draft a fix for Dana to review?
One MCP server per site. Agents read as the person who signs in, so they only see pages that person can view.
In Atlassian Administration: Apps, Sites, your site, Connected apps, Doc Drift, then Tools.
Click any Doc Drift badge and allow access. Agents act as you, so this consent comes first.
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
https://mcp.atlassian.com/forge/12e968a1-a45d-4524-ba28-d47e2315db1a
.cursor/mcp.json
{ "mcpServers": { "doc-drift": { "url": "https://mcp.atlassian.com/forge/12e968a1-a45d-4524-ba28-d47e2315db1a" } } }
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.
Built to be trusted
Doc Drift watches and flags. It never claims a page is wrong, only that what it describes has changed.
A deterministic matcher scores each change against anchors: paths, globs, renames, removed identifiers. Same input, same result, no credits spent.
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.
Agents and tools read as the signed-in person. A page they can't view comes back as unknown, with no title.
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.
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.
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.
Get started
A site admin installs Doc Drift. Jira is optional: connect it to watch issues too.
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.
Click the badge on a runbook and accept the suggested anchors. The next merge that touches them flags the page.
Questions
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.
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.
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.
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.
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.
Doc Drift is free while it's in preview. Drafting fixes with Drift Reviewer uses Rovo credits on your own site.
Docs that agents can trust, because they know when to stop trusting them.