What a share manifest establishes: local visibility and incomplete directories

A manifest makes local batches visible; it is not a service receipt or immutable archive

Inbox save copies files/builds items before atomically writing manifest.json last. pending reads/decodes manifests to list batches, without verifying every attachment still exists or was reviewed. update can rewrite a manifest. It therefore certifies neither server submission, delivery, business approval nor immutable archiving.

Different from mixed handoff, encoding and protection

Handoff checks page stages, encoding checks serialization, protection checks write options. Here local construction visibility, missing entries and incomplete directories matter. No inbox access, cleanup or deletion occurs.

Check Verified scope Manual review Not established
Construction Copy, not move; manifest last Original versus staged copy Source moved or business message sent
Visibility Readable/decodable manifest listed List versus actual attachments Each file exists/reviewed/integrity-checked
pending failure Directory/read/decode can omit entries Actual errors/scope Empty means no material
Update Manifest can change after partial placement Current stage Permanent immutable original
No manifest sweepIncomplete conditionally attempts cleanup Absence/directory timestamp Every batch has deletion TTL
Default 3600 seconds Modification age; missing time can use distantPast Age/call time Hourly clearing/minimum one-hour retention
Removal try? is not independent success proof Actual directories/copies Secure erasure/complete collection
Service/archive Local metadata differs Actual drafts/attachments/receipts Server transaction or recipient confirmation

Synthetic local observation

A lacks a manifest and is absent from pending: that does not establish no file was copied or every copy was removed. B has a decodable manifest: inspect attachments/stage separately instead of claiming complete archiving.

Default cleanup age is 3600 seconds against modification time. Missing time can use distantPast, not a minimum hour after creation. Cleanup must be called; no timer service is added. Original/staged/remote copies retain actual permission boundaries.

FAQ

Does a manifest prove every attachment exists?

pending decodes the list, not every file’s existence/content. Verify separately.

Does an empty list prove no residual files?

No. Missing manifests and directory/read/decode failures differ.

Is 3600 seconds every material's retention period?

No. It is incomplete-directory age, not universal TTL or scheduled-cleanup promise.

Does missing modification time guarantee an hour?

No. This path can use distantPast; no creation-based minimum follows.

Is the manifest immutable?

No. Existing update rewrites it; not a tamper-proof log.

Was cleanup/upload run here?

No. Local structure review only, without access/deletion/upload or new archive service.

Reading and source

Mixed-batch stages · Encoding/internal manifest · File options · Removal scope · Start · Privacy

Save/update/pending/sweep · Cleanup invocation/placement