Engineering Docs Rot Finder

Finds the docs your codebase contradicts — dead commands, moved paths, broken links — with sourced corrections. Age isn't rot, and it never edits your wiki.

NewNew9.0 KB snapshotStarter VM
Claude Code logo

What's inside

Harness

Claude Code

Plan

Starter

vCPU

1

Memory

2 GiB

Snapshot

9.0 KB

How it works · ~3 minutes

  1. 01 · Fork

    New isolated microVM on your subdomain — creator state included.

  2. 02 · Your keys

    Log into Claude Code with your own model credentials (BYOK).

  3. 03 · Ask it to work

    Open the terminal and give it a real job. You keep what ships.

30-day money-back on your first purchase · no free trial · keys never leave the VM

About this template

The flag was renamed eight months ago

The new hire follows the setup doc, runs the documented command, and it fails. They lose a day and quietly stop trusting the wiki — which is how a wiki dies.

Meanwhile the "stale docs" audit sorts by last-edited date and flags a two-year-old page that's perfectly correct.

Rot is contradicted-by-code, not old

Age isn't rot. A two-year-old page describing something that hasn't changed is correct, and flagging it burns the team's trust. A page edited last week can be wrong.

So a page is only STALE when there's a specific thing that contradicts it — a renamed command, a deleted file, a changed default, a dead link. No contradiction found means UNVERIFIED, never "stale".

Four claims it can actually check

Most of a wiki can't be verified automatically. These four can, and they cover most of the damage:

  1. Commands — a documented flag or subcommand that no longer exists. The highest-value catch, because it wastes an engineer's afternoon.
  2. File and directory paths — referenced, now gone or moved.
  3. Links — internal links to deleted pages, external ones returning 4xx/5xx.
  4. Owners — an "owned by" naming someone no longer on your team list. Flagged for reassignment, never reassigned by guess.

Everything else lands in NEEDS A HUMAN. It won't guess whether a conceptual explanation is still accurate.

Onboarding pages rank first

By blast radius, not staleness score. A wrong setup step costs every new hire a day; a stale note on an internal tool costs one person ten minutes.

Corrections are sourced or they don't ship

Every drafted fix quotes the file:line the new fact came from. A correction you can't source is just a new wrong fact replacing an old one.

What you supply

A read-only Notion integration token shared with one page tree, plus your own Claude Code login. Or skip Notion and point it at markdown in a repo.

And the codebase the docs describe — without the code there's nothing to contradict, and it says so rather than guessing.

Where this stops

It finds and drafts. It does not edit a Notion page, publish, or archive anything — an agent silently rewriting documentation is how a wrong fact becomes an authoritative one.

It won't tell you a page is accurate (it verified four claim types, not the content), won't invent a replacement fact, won't pick a new owner, and won't call your documentation "complete".

UNVERIFIED is not a pass. It means no contradiction was found in four mechanical checks — a much smaller claim than "correct".

Verified on build: the skill, the working tree, the NEVER_EDIT_DOCS guard, the rot-is-contradiction rule and all four checkable claims are present on a fresh fork, with no Notion token shape in the snapshot. Running it on your own wiki is yours.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

  • Claude Code agent

    The upstream harness, pre-installed — same version the creator ran.

  • Starter VM

    1 vCPU · 2 GiB RAM · 10 GiB disk.

  • Creator's /persist data

    The captured persist volume is copied byte-for-byte into your fork.

  • BYOK — your keys, your VM

    Add your model API keys after forking; they live only inside your microVM.

What this agent can do

1 skill

  • docs-rot-finder

    Find engineering docs contradicted by the codebase — dead commands, moved paths, broken links, departed owners — and draft sourced…

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

  • ANTHROPIC_API_KEY

Your turn

Your own Engineering Docs Rot Finder, live in about 3 minutes.

Forking copies this Claude Codeagent into a brand-new, fully isolated microVM on your own subdomain — the creator's /persist state and all. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

Starter · fork

$25/ mo

Needs 1 of your own API key