Custom record file lifecycle

The Lifecycle

Transitions Explained

A save prepares copies before persistence, then attaches ready references in its transaction. Failed preparation or persistence abandons copies, and removed references detach them. Later disposal states describe shared cleanup that Platform has not deployed.

What Cannot Happen

Only a ready file reference may attach through a successful commit; a removed or abandoned copy is not an upload for reuse.

Concurrency and Timing

Preparation occurs outside record transactions, bounded to three files concurrently and a twenty-second deadline. Only ready references commit. Cleanup phases describe the shared contract but do not run under the pinned Platform deployment binding.