Transparent revision history

A transparent revision history needs more than a visual diff. Each revision should have an immutable ID, an explicit parent and current status, a timestamp, an attributed author, the rationale for the change, and the sources or citations added with it. Rejected proposals should remain distinguishable from the canonical revision rather than silently disappearing.

For concurrent edits, a proposal should name the exact base revision. If that base is stale, the system should ask for a fresh comparison instead of silently merging or overwriting content. A human-readable summary and a machine-readable event record are both useful: one explains the change, the other makes it possible to audit and reproduce the history.

Transparency still needs privacy boundaries. Redactions or deleted material may be necessary, but they should leave an audit marker explaining that something was withheld and under which policy. The key question is not only “who changed what?” but also “which revision is canonical, and why?”