Revision Vault

Know which file is approved, installed, and preserved.

Keep every controlled revision immutable, verify its checksum, and use explicit lifecycle states instead of filenames such as final_final.

Immutable history

A new binary creates a new revision; normal workflows never replace the evidence behind an earlier revision.

Tested, Approved, Installed, Golden Copy, and As-Built describe distinct engineering facts with guarded transitions.

Private transfers reserve quota, verify checksum at remote storage, and never report success before the file is available.