Every document is a node.
Every revision a signed record.

Five moments.
No PDF archaeology.

• When you publish a revision.
  A new version is a new record, not a renamed file.

  Approver chain captured, signatures sealed, distribution list scoped at publication. The previous version is automatically marked superseded; the chain stays browseable years later.

• When acknowledgement is required.
  Per-user, per-revision — tracked, expirable, exportable.

  Roles receive the document; receipt is a record. Outstanding acknowledgements escalate through the alert engine. Anyone reading the right manual but the wrong revision is a flagged condition, not a hope.

• When a procedure is referenced from a finding.
  The doc travels with the finding, version-locked.

  A finding cites OPS Manual Part A · Section 5 v3. Years later, when v3 is archived, the citation still resolves to the exact document state at the time of the finding — not whatever is current.

• When a review date approaches.
  Review windows are workflow events, not silent dates.

  Every controlled document has a review-due field that fires through the alert engine ahead of the date. The owner gets a heads-up, the manager gets escalation if it lapses. No document quietly ages past its review.

• When the regulator asks "who, when, what did it replace".
  The chain is the answer, exportable in one click.

  Every revision links to its predecessor, every approval is signed, every distribution is recorded. The audit pack is the data — not a PDF you assembled the night before the inspection.