Prepare and Retire Meeting Files
What It Does
Staff attach or remove packet files, or save and assemble minutes. File preparation and database attachment are separate stages. A failed or stale record save does not undo the already prepared object; cleanup owns that residue. Minutes assembly is deterministic and makes no model call.
The Flow
Stage minutes text in the workspace upload area. Prepare the file through inspection and permanent storage outside the record transaction; refuse foreign references and disallowed content. Lock and recheck the record, save its prepared reference and hash, and attach or detach assets together. Remove a packet material and detach its managed file in the same transaction. Sweep due asset rows every fifteen minutes and retire each queued file after the reference check.
When Something Fails
Stop before recording the body. An upload can remain staged until expiry. Reject the file. Staged data may remain for cleanup. Roll back the reference write. Prepared permanent content can remain unattached pending pipeline cleanup. Roll back deletion and detachment. The original material remains attached. Redeliver cleanup messages that do not settle. Unreferenced files can remain longer.
Open Design Questions
File preparation and database attachment are separate stages. A failed or stale record save does not undo the already prepared object; cleanup owns that residue. Minutes assembly is deterministic and makes no model call.