Name Things

---
name: name-things
description: Name ONE thing the market will see — a mechanism, a system, a method, a product, an offer — as a set of tested name options for the owner's pick. TRIGGER when a mechanism, offer, or product needs its market-facing name. DO NOT TRIGGER to name code identifiers or files (naming), to find the piece's core idea (big-idea), or to build the offer itself (draft-offers).
---

# Name Things

One Process: turn one nameable thing into a set of name options that survived criticism. A name is the compression of the causal chain or outcome into words the buyer repeats — the hardest line in the piece, so it is never one guess. The thing's substance comes first: for a mechanism name, the documented causal chain per /mechanism binds what the name may claim.

## 1. Fix what is being named and what binds it

Name the thing, its documented substance (the mechanism's chain, the offer's deliverables, the product's facts), and the buyer language records it must speak to. A name may claim no more than the substance documents.

## 2. Generate wide through the name generators

Run /ideate on the name, with the brainstorm spanning these generators as its cells:

    Outcome compression — the end state in two or three words
    Metaphor transfer — a concrete object or process from another domain carrying the chain's logic
    Enemy naming — the villain named, the name positioned against it
    Named-person or archetype — the method carried by a persona
    Number and specific — a count, a timeframe, a threshold from the evidence
    Coined compound — two plain words fused into one ownable term
    Buyer-phrase lift — a verbatim phrase from the records promoted to a name

## 3. Test every candidate before the refute

Cut candidates that fail: said aloud it stumbles; the buyer could not repeat it to a friend an hour later; it claims chain the substance does not document; it names the category instead of this thing; it collides with a known competitor's name from the records.

## 4. Return survivors through the shared process

/ideate's refute, iterate, and options-file steps carry the set to the owner — 3–5 names, each with the generator it came from, what it claims, and the criticism it answered.

Verification: every candidate traces to the thing's documented substance and the buyer-language records; the set spans distinct generators, not one name reworded; the spoken, repeatable, no-overclaim, and collision tests ran with cuts recorded; and survivors reach the owner through /ideate with none pre-chosen.