StagBane
Get it on the Marketplace

· StagBane blog

Stale knowledge is a problem now that Rovo reads your Confluence

Picture a runbook. Someone wrote it two years ago, when it was correct. The tool it references got replaced last year. The author changed teams. Nobody edited the page- no trigger, no owner left to notice. It still ranks fine in search.

Then Rovo reads it.

Rovo doesn't know the tool was replaced or the author left. It sees a well-formed page and treats it as a source. When someone asks a question that page can answer, Rovo answers confidently- and wrongly. Nobody flagged the page, because nothing about it looks bad. It's not a Rovo bug. It's a structural gap: your AI is only as current as the pages behind it, and Confluence has no native way to tell current pages from confidently wrong ones.

This is the ordinary condition of an active wiki, not a hypothetical. The rest of this article covers why the obvious fix- sorting by date- doesn't close the gap, and what would.

The community already knows this

None of the people quoted below are talking about any particular product- they describe the same problem independently, because it's common enough that anyone doing this work has hit it.

"If your Confluence space is messy or outdated, Rovo may amplify the wrong content."

"RAG doesn't fix bad data. It indexes it, amplifies it, and serves it with confidence."

A Reddit thread about documentation three years out of date shows the cost in practice:

"A new developer joined last week and spent two days following our setup documentation before realizing that a large portion of it no longer applies. Some of the tools we reference were deprecated in 2023, yet the docs still instruct people to install them."

"Documentation inevitably gets stale, but at this point ours is actively harmful. It consumes more time than having no documentation at all because people follow incorrect steps, break things, and then someone has to step in to undo the damage and explain what actually works today."

  • u/Snaddyxd, r/ExperiencedDevs

Another thread traces the same failure to its root cause- not age, ownership:

"we've got a ton of confluence pages for our IT runbooks and honestly its becoming a mess. most of the original authors either moved on or switched teams long ago. the pages slowly go stale as our systems change, and nobody updates them because nobody really owns them anymore."

One reader, unprompted, specced a review queue with almost exactly the shape this article describes below- before any tool answering that description existed:

"before letting it answer employees, i'd make it produce a weekly 'docs we would not trust' queue: no owner, no reviewed date, conflicting duplicate, too many caveats, referenced system no longer exists, last update older than whatever your team picks."

And the trust question itself, asked plainly:

"I always wonder, when you search Confluence or a wiki, do you actually trust what you find? Or do you just ping someone on Slack anyway?"

Why date filters miss the real problem

The obvious response to stale content is a date filter: sort by last-modified, flag anything old, review the oldest first. It's a reasonable start. It isn't sufficient, and the gap matters whether or not you ever install anything to close it.

Age is not accuracy. A page modified yesterday can still be wrong. A page untouched since 2019 can still be right- a stable policy nobody needed to change. Last-modified is when someone touched a page, not whether it's still true. Age-only tools flag the calm, correct, old page and wave through the recently-edited page that quietly contradicts the one next to it.

Date filters don't know who's accountable. A page last touched eighteen months ago might have an active owner who deliberately left it alone- or no owner at all, because the author left the company two reorgs ago. Two very different risk profiles, the same timestamp.

Review dates are voluntary, and they lapse. A review date tells you when someone last vouched for a page, not whether that still holds, or whether the page changed the day after. Treat it as a data point, not proof.

Orphaned pages are invisible to a date filter. A page with no incoming links from anywhere in your space won't surface through navigation, but Rovo can still retrieve and cite it. Date has no concept of "connected to the corpus" versus "floating, forgotten, still indexed."

Contradictions between pages are invisible to any metadata filter. Two pages on the same topic, written months apart, saying different things- no timestamp catches this, since both can look current. Catching it takes reading both and comparing claims: a semantic judgment, not a metadata query.

The honest summary: a date filter surfaces candidates. It doesn't triage by risk, doesn't explain why a page needs attention, and can't tell you whether it's accurate. Ownership decay, not age, is the root cause- pages go stale because the person accountable for them stopped being accountable, and nothing records that this happened.

What an explainable review queue looks like

The alternative to a date-only view is a queue that reasons over more than one signal, and says plainly why each page landed where it did.

Four bands, one explicit rule set, no score. Every audited page lands in Critical, Stale, Watch, or Healthy, assigned by an explicit, ordered rule set: the first rule that matches decides the band. No composite number sits behind this- a numeric health score is exactly the failure mode this kind of tool should avoid, since it hides the reasoning behind it. Every row instead states, in one plain sentence, the rule that placed it- an answer you can send to a page owner, or disagree with by marking the page Verified Current.

Five signals, each meaning something different. Age is necessary but not sufficient. Owner presence distinguishes an active owner from none at all. Review state tracks whether anyone vouched for the page recently, separate from whether anyone edited it. Orphaned status flags pages with no incoming links from the audited space- invisible to navigation, though nothing in Confluence stops Rovo from still indexing and citing them. Broken internal links flag pages pointing at pages that no longer exist, scoped to links inside audited spaces only. Some rules escalate to Critical when problems compound- broken links plus no owner, no age requirement, so a page edited yesterday can still be Critical.

Non-destructive by design. The queue surfaces, flags, labels, and requests. It never archives, deletes, or rewrites page content- every action is something a human chose to do.

A reader-facing trust signal. Every audited page carries a byline badge visible to any reader, soft and positive-only: a green "Verified" lozenge with a date appears only when a human vouched for the page within the review window. Other pages show a neutral marker; a merely-Healthy page is never labeled "Verified"- nobody vouched for it. It shows verification recency, not edit recency. Bands aren't shown to readers; only a site admin opening the badge sees the full band and reason.

A coverage view for the whole space. Admins also see a per-space Rovo-readiness view: band distribution plus a headline "Rovo-trustworthy %," the Healthy share of monitored pages- a coverage figure always shown with its per-band counts, never a per-page score.

Requesting a review, without a storm. A one-click action posts a templated comment naming the owner and every reason the queue holds against the page, capped by a Request Budget so it can't flood notifications. A request resolves when the page is marked Verified Current or gets a new version, or the owner replies "Verified." A "Stale" reply records the owner's verdict- overriding the automated signals- but leaves the request open.

The question the queue can't answer- and the agent that can

The deterministic queue tells you a page is at risk. It can't tell you whether the content is still correct- a semantic question, requiring something to read the page and reason about whether it matches reality. That's where an on-demand Rovo agent, "Page Health Auditor," comes in as an optional second opinion, not a replacement for the queue.

The agent, open to any licensed Rovo user in Rovo chat, has three categories of action: read-only audits (check one page, compare two for contradictions, search for overlapping pages), confirm-to-act actions (mark a page Verified Current or Stale, request an owner review, toggle needs-review- only on explicit confirmation), and admin-only views (a ranked stale-page list, the space Rovo-readiness figure)- plus one admin-only advisory-marker action. Ten actions total, though the category shape matters more than the count.

The trust properties matter as much as the actions. The agent reads as the person asking it- it can never see a page that user couldn't already open. It never persists an opinion: every verdict is chat-ephemeral, cited to the page version judged, gone once the chat ends. Any write it performs is one of the queue's own non-destructive actions, only on confirmation- it never edits, archives, or rewrites content, and it runs on the customer's own Rovo credits, inside Atlassian.

One action is easy to overstate: an admin can flag a page for AI governance with an advisory marker. StagBane's agent and badge honor it, but it doesn't remove a page from native Rovo answers or search- no such native mechanism exists. For hard exclusion, the only lever is Confluence's page permissions.

Trust the queue over the agent if you have to pick one- explicit, auditable, reproducible in a way a chat verdict isn't. Use the agent on the pages that matter most: Critical band, ones headed to an owner, ones you suspect contradict something else.

The trust architecture underneath it

None of this helps a security-conscious admin if the tool itself is a new risk. This runs entirely on Atlassian infrastructure, built on Atlassian Forge, with no external servers and no developer-controlled network calls. Page body text is read only to extract internal links, then discarded- never stored. There's no telemetry, and no Personal Access Tokens are required or used. What it stores- page metadata, signals and bands, the link map, review-request history, scan status- lives in one Forge-managed database per install, inside Atlassian. Nothing leaves.

After an uninstall, labels and comments the tool applied stay on your pages. Its own stored data is soft-deleted, with a 21-day window during which reinstalling relinks it; Atlassian doesn't publish an exact permanent-deletion timeline, so this article won't invent one.

Who this is for, and who it isn't

The review queue is an admin surface- a site admin or knowledge manager, not every end user. The Rovo agent is open to any licensed Rovo user, so that conversation isn't gated the same way. It works on Confluence Standard and above- no Premium required, no free tier, no help on Confluence Free. If what you need is external link-checking, that's out of scope- the signals above are internal-link only, by design.

Getting a corpus Rovo-ready

Everything above describes a general shape: a queue reasoning over ownership, review state, orphaning, and broken internal links instead of just age, plus an optional advisory agent for the semantic question metadata can't answer. That's what StagBane, the Page Health Auditor for Confluence, builds.

StagBane is a Forge app for Confluence Cloud, at v1.0. It scans nothing until you choose which spaces to audit, bands every page using the rule set above, and gives every admin the reader-facing badge and Rovo-readiness view. The Rovo agent is an optional second opinion, not the thing you're buying.

It's one paid edition, about $1 per user per month (roughly $10 a month in the 1-10 user range), with a standard 30-day free trial through the Atlassian Marketplace and no free tier. The Marketplace listing is always the authoritative current price.

More from the blog · Get StagBane on the Atlassian Marketplace