
Knowledge base maintenance that doesn’t rot
An article goes stale because it has no owner and no date by which anyone was going to look at it again. This is how an agent holds both, watches the sources, and publishes nothing itself.
The article was true when it was written
No owner, no date, and two articles that disagree
- The article was true when it was written.
- Nobody decided to let it go stale; it has no owner and no date by which anyone was going to look at it again, and the thing it describes moved.
- Now two articles say different things and both of them look official.
- Meanwhile the question people actually keep asking has never been written down at all.
An owner and a review interval on every article, and a watch on what they depend on
- Staleness stops being a discovery.
- A source change reaches the article that depends on it.
- The owner edits rather than rewrites.
How an agent runs it
Staleness needs something to be measured against. This workflow puts an owner and a review interval on every article, then watches what those articles depend on.
Holds
Watches
Finds
Drafts
Human gate
Records
Surfaces
What changes when staleness is measurable
Staleness stops being a discovery
A source change reaches its article
The owner edits rather than rewrites
Where this fits
Tier 1 through the Automate a Workflow door: one process end to end, from an article inventory to an update its owner publishes. What is true and what is published belong to a person, and the workflow never becomes the authority on either. The executive assistant layer is the possible next step rather than a promised state once this sits alongside a seat's other standing work; How It Works shows how the ownership gate is built.
