# Make every bot confirm the current process version before its write tools open

PaperChase agent use case (free feed entry), version 1.0. Source: [Philipp M. W. Hoffmann (@malmaladei)](https://x.com/malmaladei/status/2115455350849577424), 2026-10-28.

## What they did

Instead of pasting process rules into each bot's prompt, he keeps one skill per process in a registry served by his MCP server. A bot reads the skill, acknowledges the version it read, and only then do the write tools for that process accept its calls. Changes to a skill come in as diffs, the critical ones need the owner's approval, and a process page shows which bot is running which version.

## Worth knowing

The useful move is making the server enforce the rulebook rather than trusting the prompt: an out-of-date bot cannot write, so a rules change reaches every bot or blocks it. This is one operator's description of his own setup, without code or numbers, so treat it as a design pattern to copy, not a product.

## Workflow template

```text
Apply this workflow to [your project]:
1. List each business process your bots touch and write one skill file per process with a version number.
2. Serve the skills from your MCP server and record which version each bot acknowledged.
3. Make write tools for a process refuse calls from a bot whose acknowledged version is not current.
4. Accept skill changes only as diffs, and require your approval on the processes that move money or reach customers.
5. Keep one page that shows each bot, its job and the version it runs.
Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
```

## Steps

1. **List each business process your bots touch and write one skill file pe.** List each business process your bots touch and write one skill file per process with a version number.
2. **Serve the skills from your MCP server and record which version each bo.** Serve the skills from your MCP server and record which version each bot acknowledged.
3. **Make write tools for a process refuse calls from a bot whose acknowled.** Make write tools for a process refuse calls from a bot whose acknowledged version is not current.
4. **Accept skill changes only as diffs, and require your approval on the p.** Accept skill changes only as diffs, and require your approval on the processes that move money or reach customers.
5. **Keep one page that shows each bot, its job and the version it runs.** Keep one page that shows each bot, its job and the version it runs.

## Credit

Workflow reported by Philipp M. W. Hoffmann (@malmaladei): https://x.com/malmaladei/status/2115455350849577424

Summary and template written by PaperChaseWebb in our own words. Questions: mgmt@paperchasewebb.com