Hidden file

How it works

If the contract includes it, the packager must include it. If it should not travel, the packager must exclude it on purpose. .DS_Store and Thumbs.db are the usual noise. Sidecar dotfiles can be the edit data.

A job skips dotfiles and drops .env into oblivion, which was intended, and also drops .ratings.json, which was the grade. The manifest did not list dotfiles. They add an explicit include.

How it differs

Hidden is a client display flag, not a permission. The server may still store it.

A zip that adds hidden AppleDouble files annoys the recipient.

Decide in the packager.

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 hidden file, 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 hidden file 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.