Operating Guidance for Export Before Completion
The export is not a test of the file. It is a test of whether the work can be called something.
FIELD GUIDE TO EXPORT BEFORE COMPLETION
A guide for identifying, documenting, and understanding the behavior in its natural habitat
Stage 1: Initial Conditions
The subject has opened a file. The file is unfinished. The unfinished state is known and is not the problem; the problem is the uncertainty attending it. Unfinished work cannot be evaluated, shared, or pointed to. It exists only as potential.
The subject opens the export menu.
This is not a mistake. It is an assessment. The subject is determining whether the file, if it were finished, would export correctly. This is a reasonable question. The reasonable question is being asked now, before there is anything to export, because the export settings represent something the subject can control.
Content is not yet in that category.
Stage 2: The First Export
The file is exported. It is incomplete. The exported file is a record of an incomplete state, labeled with a filename that implies finality. The subject does not open the exported file. It goes into a folder.
Export before completion creates a small sense of control. The sense of control functions as a proxy for progress. It does not track progress. It precedes it.
Stage 3: Proceduralization
The export step was done once before the work was ready. The work was completed later. The work was eventually exported in its final form. On a subsequent project, the subject exports early again. This is not repetition for its own sake; there is no conscious decision to repeat. The step is simply present in the procedure, the way earlier steps are present.
The sense of control becomes something the subject checks for before trusting the ordinary process.
Stage 4: Ritual Status
By the end, losing the ritual feels more alarming than the original problem it was meant to solve. The original problem was uncertainty about whether the export settings were correct. The settings have been correct every time. The check is now performed to confirm a thing that has never been false.
Familiarity may certify export before completion even when efficiency cannot. The export happens. Nothing is exported. Something is done.
Stage 5: Succession
The subject describes their workflow to a collaborator. They include the early export as a standard step. The collaborator adopts it without asking why. The collaborator will not need a reason. They have a precedent, which serves the same function.
Field notes complete. No recommended intervention. The export will happen again on the next project.