Document Set Management

Manage relationships and persistent source contracts across documents. A document set needs more than individually clear prose, but small collections need not acquire a complete governance system before a useful edit.

Establish the source map

Read existing documents, manifests, registries and Git changes. Identify canonical roots, derivatives, audiences and unresolved source conflicts. Preserve existing metadata formats where practical. Bootstrap only the relationships needed for the current decision; grow registries through use, not numerical quotas.

A useful manifest records document ID/path, audience/purpose, source role, lineage and version. For consequential repeated claims, record canonical wording, source location and affected derivatives. Section-level edges improve impact tracing when document-level lineage is too coarse.

Choose the workflow