Give AI drafts a waiting room before they become instructions

Our documentation handbook gives unreviewed assistant output a separate home. Promotion into a guide is a decision about evidence, ownership and maintenance.

An assistant can produce a convincing guide before the team has decided whether its commands are correct. That speed is useful, but it creates a records problem: a polished draft looks much like an issued instruction. Our 29 October repository handbook gives those two things different homes.

A place to think without issuing a procedure

Raw assistant output stays in an intake area until a named reviewer validates it. The handbook calls for review of commands, links, impact, ownership and rollback effects before operational material enters its controlled home. A draft can therefore remain useful without borrowing the authority of a runbook.

I read this as a practical publishing rule. The location should tell a future reader whether the material is a suggestion, a record of an event, or an instruction the team has accepted. Formatting alone cannot carry that distinction.

The model name is not the evidence

Moving between AI tools should not change that review boundary. Each tool may have its own session memory and preferred instruction format. The maintained document needs an owner and a source that survive the session. If its accuracy depends on remembering which chat produced it, the handover is incomplete.

Before promotion I want to know what claim each source supports, which parts were actually checked, and which remain proposals. A command that was read is not a command that was run. An explanation of a rollback is not evidence that the rollback was exercised.

Promotion includes the maintenance job

A new guide also creates future work. Someone must update its links, keep its examples aligned with the application and retire it when the procedure changes. I would rather issue a short, owned guide than a comprehensive page nobody knows how to maintain.

The handbook also keeps application files and private material outside the documentation workspace. That helps the written record keep its purpose: explain and reference the operational system, rather than become an accidental second copy of it.

For a team using several assistants, my advice is to make the promotion step explicit. Keep the useful drafts. Review the instructions. Record who accepted them and what was checked. The waiting room makes experimentation easier because a draft can be explored without quietly becoming policy.

Earlier Dockeeper records: the documentation spine, one page, one job, and reading our AI architecture end to end.