Your wiki is a camera roll.

Right now, in your phone, there's a photo of someone you love next to a screenshot of a Wi-Fi password from a hotel you'll never visit again. They're stored the same way. They take up the same space. If you search "August 2024," they show up side by side.

Your phone doesn't know one of those is permanent and the other was useful for ninety seconds.

Neither does your wiki.

In 1999, a roll of Kodak Gold cost you 24 exposures. Each frame was roughly fifty cents — film, developing, prints. You composed the shot. You waited for the light. You pressed the shutter knowing that frame was spent whether the photo turned out or not.

Fifty cents and a finite roll meant you didn't photograph your parking spot. You didn't take eleven shots of the same angle to pick the best one later. The economics of film were a quality gate disguised as a limitation.

Digital cameras lowered the barrier. Storage was cheap, the LCD preview was instant, you could take two hundred shots on a vacation instead of twenty. But there was still a natural pause in the system. You had to get the photos off the camera. Find the USB cable, plug into the laptop, open the import dialog. In a pre-cloud world, that ten-minute ritual was a moment of implicit curation. You'd skip the blurry ones. You'd drop the rest into a folder called "Beach Trip 2007" and move on.

Then the phone ate the camera, and the cloud ate the folder.

Suddenly the marginal cost of a photo was zero and there was no transfer step. The shutter, the storage, and the archive were the same device. Every photo you took was instantly, permanently, undifferentiatedly saved. A photo of your kid's first steps lived in the same infinite scroll as a screenshot of a tracking number you needed for forty-five minutes.

The filing cabinet era was film. Creating a document had real friction — typing, printing, routing, filing. Nobody walked a memo to the filing room unless it mattered enough to justify the effort.

The wiki era was the digital camera. Creating documents became easy, but there was still friction. You had to choose a space, build a page, format it. Enough to make you pause and consider whether the thing was worth writing down.

The AI era is the phone. Meeting transcripts auto-generated. Status updates drafted from chat threads. Documentation written from a prompt. The marginal cost of creating a document is approaching zero, and the transfer step — the moment where a human decides whether this deserves to exist in the knowledge base — is disappearing.

The volume is about to explode. And just like your camera roll, the system has no concept of the difference between a compliance policy that will govern your company for the next decade and a meeting summary that nobody will ever read again.

But the acronym, clinical as it is, understates the problem. ROT isn't just clutter. It's an erosion of trust.

Think about the last time you searched your company's wiki for a procedure. You found three pages with similar titles. One was from 2019. One was from 2022. One was a draft that was never finished. Which one is current? Which one reflects actual practice? You don't know. The system doesn't know. So you message a colleague and ask them. The wiki becomes a suggestion engine that you verify through human conversation, which defeats the entire purpose of having a wiki.

Now add AI to this system. An AI agent that ingests your knowledge base doesn't check the "last updated" date and squint skeptically the way a human does. It treats the 2019 procedure with the same confidence as the 2025 one. It can't tell the difference between an active policy and an abandoned draft.

If you're like most people, you have a "Favorites" album with eleven photos in it from 2021 when you briefly tried to maintain it. You might have one vacation album that's half-complete. And then there's the undifferentiated stream of 14,000 images you scroll past every day.

The tools exist. The discipline doesn't. And it doesn't because curation is a separate chore from creation.

Any task separate from the main workflow, with no immediate consequence for skipping it, will not get done at scale. This isn't a character flaw. It's a structural certainty. The behavioral economics are unforgiving: the future cost of disorganization is abstract, but the present effort of organizing is concrete. The degradation is so gradual you never hit a crisis point that forces action. You just slowly stop trusting the system.

Your wiki is exactly the same. You could archive old pages. You could set review dates. Every wiki has an "archive" button somewhere. Nobody clicks it. For exactly the same reasons nobody maintains their photo albums. The curation is disconnected from the creation, so the curation doesn't happen, so the ROT compounds quarter over quarter until people stop trusting the wiki — and then stop using it — and then the organization's knowledge reverts to what it was before the wiki existed: tribal, oral, locked in the heads of people who might leave.

In a well-designed game, information exists in layers. The HUD shows you what matters right now — health, ammo, your next objective. It's designed for a glance. You should never have to stop playing to understand it.

But the game has vastly more information than what's on the HUD. Your full inventory, your quest log, your character stats — all of that exists, all of it is accessible, but it lives behind a deliberate action. You press a button. You go looking for it because you need it.

Stephen Few, the pioneer of dashboard design, formalized this as progressive disclosure. Present essential data first, with supporting detail available on demand. The insight isn't about hiding information. It's about respecting the cognitive cost of attention.

When every document in your wiki looks the same — same font, same placement, same weight in search results — the critical and the trivial compete equally for attention, and attention is finite.

These aren't filing categories. They're expectations about the future relevance of information. Right now, no knowledge tool captures them. Every document is treated as equally permanent, equally current, equally prominent from the moment it's created until someone manually intervenes — which is never.

Critically, durability controls visibility, not existence. A document that fades from the glance layer isn't deleted. It's still in the archive. It's still in the version history. If you need it, you can find it. The same way you can open your game's quest log to review a completed quest, or scroll deep into your camera roll to find that photo from three years ago. But it's not competing for attention in the default view. It's not showing up alongside current documents in search. It's not being ingested by an AI agent as if it's still authoritative.

A Q1 roadmap becomes outdated when the Q2 roadmap is published. A runbook becomes unreliable when the service it describes is updated. A draft is fulfilled when it's formally approved and promoted. A policy needs review when the regulation it implements changes.

These are events, not dates. And they form dependency chains. One event at the root propagates through the entire knowledge graph.

No knowledge tool today does this. Not because it's technically impossible, but because no tool today models the relationships between documents as first-class objects. Links in a wiki are navigational — they help humans click from one page to another. They don't carry semantic weight. They could.

What if the act of sharing a document also classified it? What if putting a document in a collection automatically set its expected lifespan? What if publishing a new version of a plan automatically marked the old version as superseded? What if the system noticed — without anyone asking — that a procedure references a policy that's been archived, and flagged it the way a compiler flags a broken import?

That's not curation as maintenance. That's curation as a byproduct of use. The album that builds itself — not because AI magically understands your intent, but because the system's architecture makes curation the path of least resistance rather than an additional chore.