Object lock

How it works

Compliance mode ignores even an admin delete. Governance mode allows a privileged bypass. A transfer into a locked bucket cannot be quietly replaced. That is the point.

Invoices land in a bucket locked for seven years. A script that used to overwrite last month's file now fails. They write a new key per month. An auditor reads last March's object unchanged.

How it differs

Object lock is not file encryption. It stops deletion. It does not hide contents.

A legal hold is a related flag that outlives the clock.

Do not lock a drop folder you must clean weekly.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For object lock, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive object lock files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.