Character Name Ideas Template 1
Expansion engine: Start with [prompt], choose [specific context], add [constraint], and decide what changes by the end.
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Strong character name ideas are specific enough to begin drafting immediately, varied enough to support different voices and experiences, and open enough that two writers can produce meaningfully different pieces from the same starting point.
Expansion engine: Start with [prompt], choose [specific context], add [constraint], and decide what changes by the end.
Argument engine: Turn [prompt] into a bounded question, choose a claim, give two reasons, and address one counterpoint.
Observation engine: Use [prompt] to notice five concrete details, then explain the pattern or meaning connecting them.
Variation engine: Rewrite the same prompt for a different audience, time scale, point of view, or genre.
Provenance and classification audit for Character Name Ideas: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
Source-record and update audit for Character Name Ideas: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Source-ledger and revision-history audit for Character Name Ideas: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].