Image
Workflow
Back office

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

Today

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.
With agents

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.

01

Holds

Keeps the inventory of articles with an owner and a review interval on each.
02

Watches

Follows the sources an article depends on, and names the article whose source has moved.
03

Finds

Surfaces the article nobody has reviewed inside its interval, the one nobody owns, the duplicate pair, and the two articles that contradict each other.
04

Drafts

Writes the proposed update from the records you authorize, with the change and the source of the change shown side by side.
05

Human gate

No article changes without its owner. It publishes nothing, edits nothing and retires nothing, every draft goes to the owner to publish, edit or retire, and the review can be done by hand at any point without the agent because the articles and the sources are yours.
06

Records

Keeps what was reviewed, changed or retired and when, so staleness is a state on the record rather than a discovery.
07

Surfaces

Reports the question people ask that no article answers, as a gap for an owner to fill or to close.

Results

What changes when staleness is measurable

Staleness stops being a discovery

Every article carries an owner and a review interval, and the ones outside their interval are reported like any other gap.

A source change reaches its article

The dependency is held on the record and watched, rather than remembered by whoever wrote the article.

The owner edits rather than rewrites

The update arrives drafted, with the change and its source shown together.

Where this fits

Workflow / Automate a Workflow

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.

Tier 1 / Prove
How It Works

Questions, answered

No. It drafts, and the owner publishes, edits or retires. Nothing changes without its owner, the gate is closed by default, and the articles and the sources live in your systems, so the review can be done by hand at any point without the agent.

AI Opportunity Audit

See which of them have an owner and a date

Bring the five articles your team relies on most, and see which of them have an owner and a date.