Starter templates must look unlike user-created work

What it is

Once a starter lives as a real record, it shares a list with objects the user later creates. Distinction means origin remains scannable: a badge, a zone, a “from template” subtitle—not a hope that people remember which file arrived at the door. This is not the same as badging sample rows “demo.” Samples should not remain in the true list. This is about a seed that is allowed to stay, and how to keep it from collapsing visually with handmade work.

Why it happens

Lists organize by name, time, and thumbnail, not by biography. A seed titled “My project” with a finished-looking cover is classified as delivered work: people dare not edit it, or they believe they wrote what they did not. Origin has to live on the object, not only in a welcome sentence at create time—the sentence is forgotten, the object remains. Distinction must also survive rename: after the seed takes a business name, the origin badge should still be inspectable, or biography dies at the first rename. Distinction that is too strong (a locked zone that cannot open as an ordinary object) fights the job of continuing on the start, so distinction is a mark, not isolation. After substantial editing, the badge may recede into a property line, but while the default title and cover remain, it must be loud.

Where it stops holding

A template the user picked from a library has known origin at create; list marking can be quieter. A seed the system slipped into the workspace must be louder. In a team space the seed is a starter for the creator and “a file already here” for someone who joins later; marking must let joiners read origin too, or they will take it as a colleague’s finished piece. A fully blank starter (structure, no copy) is rarely taken as completed work; a mark only in file info can suffice.

Applying it

• Mark system-placed starts as “template / starter” in the list, title bar, and properties. Avoid default titles like “My…” that already sound owned.
• After rename or cover change, keep origin openable in properties; do not write biography only on a one-shot welcome bar.
• Do not lock the seed in an uneditable demo zone; the object opens as an ordinary record while the mark exists.
• Verify in a list that already contains user-created items: ask someone who did not create them which ones the system placed. Mis-pointing, or fear of editing the pointed file, means distinction is too weak.

Related

• Within the group: H2.08.1 Starter content is an editable start; samples stay out of the record · H2.08.3 People often read starter content as personalized output · H2.08.4 Starter content must resemble real work or it fails as a model
• Adjacent: H2.06 Sample Data · H8.10 Marks, tags, and classification · G1.08 Terminology consistency
• Search terms: template origin · starter badge · seed vs created