Introducing StagBane- find what is stale before Rovo treats it as truth
Today I'm launching StagBane- Page Health Auditor for Confluence, v1.0, on the Atlassian Marketplace. Here's why it exists, what it does, and what it deliberately does not do.
The problem
Every Confluence space accumulates pages that nobody owns, nobody has reviewed in years, and nobody has touched since the policy changed. Until recently, that was a knowledge-quality annoyance you could live with.
Now Rovo reads those pages and answers questions from them. A confidently wrong page becomes a confidently wrong AI answer- and the person asking never knows the source was two years out of date.
Date filters can tell you a page is old. They can't tell you whether it's still accurate, whether it contradicts another page you published last month, or whether anyone still owns it. And they can't explain why they surfaced it. I wrote the long version of the argument here if you want the full case.
What StagBane does
The queue comes first, because the queue is the product.
Every audited page lands in one of four bands- Critical, Stale, Watch, or Healthy- by an explicit, ordered rule set. First match wins. No composite score, no mystery algorithm. Every flag gets a one-sentence reason, something like "no owner assigned, no current review on record, last modified over a year ago." You always know exactly why a page is there.
The bands come from five deterministic signals: age since last modification, owner presence or absence, review state, orphaned pages (no incoming links within your audited spaces), and broken internal links. The queue has a broken-link report and filter, plus a CSV export that respects whatever filters you've applied- the report you're looking at is the report you export.
Around that queue is a workflow loop, not just a list. Request Owner Review posts a templated comment @mentioning the page owner, governed by a Request Budget so notification storms are structurally impossible. The owner can reply "Verified" or "Stale" right in the comment thread to resolve the request- no queue access needed. Review windows have a default cadence you can override per space. An unanswered request can escalate an at-risk page, and admins can suppress a specific reason on a specific page when it's genuinely fine- every suppression logged, and auto-invalidated the moment the page changes. A weekly digest, in-product only, groups the needs-attention set by owner.
Every audited page also carries a trust badge in its byline- soft, positive-only. Readers see a green "Verified" badge only when a human vouched for the page within the review window, and a neutral marker otherwise. It shows verification recency rather than edit recency, and it never shows the underlying band to readers. For admins, there's a Rovo-readiness view per space: a "Rovo-trustworthy %" figure, defined plainly as the Healthy share of monitored pages, always shown with its per-band counts- a coverage figure, never a per-page score. Admins can also flag a page with an advisory rovo-ignore marker: StagBane's own agent and badge honor it, but it doesn't touch native Rovo indexing- for that, you still use Confluence's own page permissions.
Last- because it's the second opinion, not the headline- there's an optional Rovo agent, "Page Health Auditor" in Rovo chat. Once the deterministic queue has surfaced the candidates, the agent answers the question no date filter can: is this page still accurate, and do these two pages actually contradict each other? It offers read-only audits, confirm-to-act actions, and admin-only aggregate views (ten actions, if you want the number). It reads as you, so it only ever sees what you can already access, and it never edits page content on its own- any change happens only on your explicit confirmation, through the same non-destructive actions the queue already offers.
Why trust it
StagBane is built 100% on Atlassian Forge. Nothing leaves Atlassian- no external servers, no external network calls, no developer-controlled egress. Your page body text is read only to extract internal links, then discarded; we never store page content. There's no telemetry of any kind, and no Personal Access Tokens are required.
The queue is non-destructive by design: it adds labels and comments and records review marks. It never touches your content beyond that- you decide and act.
What it doesn't do
Some of this is as important as what it does:
- It does not archive, delete, or rewrite content. Ever.
- It checks internal links only. No external-link checking.
- It does not give you a numeric per-page health score- by design. A number that can't tell you why isn't an answer.
- The advisory
rovo-ignoremarker is honored by StagBane's own agent and badge, not by native Rovo- it is not a native exclusion mechanism. - The Rovo agent is on-demand. It doesn't run automatically and it isn't monitoring anything continuously.
Who it's for, and what it costs
StagBane is for Confluence site admins and knowledge managers who want to see which pages are most at risk of misleading readers- and now misleading Rovo. It works on Confluence Standard tier and above; Premium is not required.
Pricing is one paid edition, about $1 per user per month (about $10/month at the 1-10 user bracket), with a standard 30-day free trial and no free edition. The Atlassian Marketplace listing is always the authoritative current price.
Try it
Install StagBane from the Atlassian Marketplace, or start with the quick-start guide if you want to see how the queue reads before you install anything.
Questions, feedback, bug reports- all welcome. I built this because I wanted it to exist. I hope it's useful to you too.
- the StagBane developer