Templates must be editable, not only fillable

What it is

Tap “write the weekly note,” and a whole prompt plus sample sentences dumps into the field. Send lights up. The structure itself is locked — you cannot delete “highlights this week,” cannot rename “risks” to “commitments to customers.” That is fill-and-apply. Editable templates require that once a template is on the surface it is still a draft: structure, slot names, order, and cuts sit inside the user’s authority. Apply is only the default start.

Editable is not “an extra remark.” A remark is a bypass the model may ignore. Editable means the main structure can be handled. It is also not “the structure must be visible or nothing is learned” — that is a learning problem. This is control: whether someone can pull the frame down and re-nail it.

Why it happens

An uneditable template demotes the user to a clerk filling blanks. Clerks do not own the structure. If it is wrong they can only blame the words they typed, not the frame. Frames for generative tasks are often wrong: this team writes “blockers” not “highlights”; this person’s weekly has no “risks,” only outward commitments. Without ownership the only legal move is to accommodate the frame, and the artifact accommodates a task that is not theirs.

Skill freezes as well. People who only ever apply, never edit structure, cannot turn the template into their own tool. Editability is the only channel from official structure to personal structure. Block it, and the template stops at a one-shot wizard.

Studying it

Two templates, same content: one fully editable after dump (including cuts and renamed slots), one with values open and skeleton locked. The task is deliberately partly misaligned with the skeleton (one extra dimension, one official column missing). Dependent variables: whether the skeleton is edited, type of edit, match of the final to the real task, subjective “is this still my weekly.” Further independent variables: whether editing the skeleton requires an “advanced” mode, whether a preview of the rewritten prompt is offered before send.

Code “changed a slot value” apart from “changed the structure.” Value-only still counts as apply. True editability is operationalized as structural change.

Where it stops holding

Legal instruments, regulatory filings, and outbound mail under a forced brand voice lock structure for compliance; editability becomes a risk. One-shot consumer tasks (“remove the background of this image”) have no skeleton worth editing; editability is extra chrome. In knowledge work the same template runs dozens of times, and the cost of uneditable scales with use. Shared templates that anyone can restructure will also destroy common meaning — that needs permission layers, not turning editability off.

Applying it

• A template dumped into the field should be fully editable by default. Mark the skeleton with light cues (highlighted slot names), not read-only blocks.
• Deleting an official column must be a first-class action, not buried under Customize. After deletion, the prompt must not secretly put the column back.
• Save “this frame I edited” as a personal template. Otherwise editability lasts one turn and the next turn reverts to official apply.
• Check: a real task misaligned with official columns. If more than half the finals still keep a column people said out loud “we don’t write that,” the template was only applied. Then check whether a deleted column returns as a corpse in the model output — if it does, editability never reached generation.

Related

• Same group: L2.03.1 Templates lower the cost of getting started · L2.03.2 Templates constrain the range of what users will express · L2.03.4 Templates turn open input back into structured blanks, at the cost of openness · L2.03.5 Placeholder content in templates is kept verbatim; empty slots must be unskippable · L2.03.6 Templates encode the designer’s task assumptions and actively mislead when those do not match real work · L2.03.7 A template that can only be applied whole, with its structure invisible, teaches nothing
• Nearby: L2.05 Iterative Revision · L2.06 Granularity of Control · L2.07 Prompt History and Reuse
• Search terms: editable templates · template as draft · structural ownership