After abort, ownership of what was already generated must be clear: usable, redo, or void

What it is

Someone hit stop. Half a function sits in the editor, with no sentence saying: keep editing, void the lot, or you must generate again. Some people use the slice as a draft; some dare not touch it for fear of an illegal structure; some refresh and find the slice gone. Ownership of aborted partials requires that the leftover slice be explicitly labelled usable draft, must-redo, or void, and that behaviour match the label.

That stop exists, and that stop is the main gain, do not answer what the leftover is after the stop.

Why it happens

Abort cuts an unclosed generation at a human boundary. A slice may be a legal draft in prose, an unparseable prefix in structure, an intermediate that must not persist in sensitive content. If the UI keeps it in a “result” region, people will use it as a result; if stop clears it, people treat abort as costly and the gain of stopping early is scared off.

When ownership is vague, three groups each follow a silent policy, and afterwards one cannot audit whether the slice counts as system output. Responsibility, persistence, and overwrite on regenerate all need to know which kind of object it is.

Studying it

Abort on prose, code, and sensitive tasks; compare keep-as-draft, clear-as-void, force-regenerate. Dependent variables: willingness to abort, times the slice is misused, conflicts when regenerate overwrites human edits. Independent variables: whether the structure had closed, sensitivity, whether a label appears.

Willingness to abort must be measured. Ownership policy feeds back into whether people dare to stop.

Where it stops holding

When people stopped because “this is already enough,” the slice is the result they wanted and should go as a usable draft. When they stopped because of drift or sensitive content, the slice should be voided and kept out of history. An unclosed structure must not default to usable unless there is an explicit “fix until parseable” action. A system interrupt (dropped network) is not the same ownership as a user abort; do not share copy. This entry does not treat whether the control exists.

Applying it

• At the moment of abort, surface a three-way status; do not go silent: keep as draft / discard / continue generating from this slice.
• Unclosed structure should not, by default, copy into a parsing downstream; the draft is for human reading.
• Discard must actually leave the result region and the history. Sitting in “result” while labelled void is still false ownership.
• Check: after abort, ask “can this slice be delivered.” If the answer disagrees with product policy, or no policy appeared, ownership is not clear. Then count people who dare not stop — if policy is “stop and it’s gone,” early abort will be suppressed.

Related

• Same group: L3.11.1 The value of streaming is an early signal one can judge, not a shorter total duration · L3.11.2 People can abort from early content; abort rights are streaming’s main gain · L3.11.3 Incomplete and complete content must be visually distinguishable · L3.11.4 Structured output passes through temporarily illegal intermediate states while streaming
• Nearby: L3.06 Streaming Presentation · L3.12 Editing and Taking Over Generated Content
• Search terms: aborted partial · ownership after stop · keep or discard stream