Prepare a handover another editor can use

Context and provenance

Create a short handover bundle with the current release, a dated content inventory, a source-review list and examples of accepted, rejected and withdrawn contributions. Include the reason for each example. Describe how record IDs remain stable across updates, and distinguish creative source fragments from documented history and personal imports.

Write down the actual operational boundaries: where private data is stored, how a backup is restored, which connector is enabled and who owns the credentials. Transfer secrets through an appropriate private channel, never inside the public application ZIP. Include unresolved issues and the next safe action for each one. A missing credential and a missing feature are different blockers.

Ask the next editor to complete one ordinary task using only the bundle: locate a record, assess a contribution or restore a copy into an isolated test environment. Watch where the instructions fail and improve them. W3C's provenance work emphasizes describing the production of information; this original handover exercise extends that idea to the practical continuity of an editorial service.

Sources and evidence

1. W3C: PROV overview