Character naming decision brief

Make a decision before collecting names

A request such as memorable, secretive and connected to the family sounds specific until you try to reject a candidate. Does memorable mean easy to spell after one exposure, distinct from the other speakers, or meaningful after a reveal? Does connected mean a shared surname visible in chapter one, or a marker readers can understand only later? A useful naming brief turns those wishes into obligations with places to test them.

This workbench produces a decision plan rather than a list of names. Give it one character's narrative action, the period you have authored, the language or evidence scope, and typed requirements. It separates mandatory conditions from preferences, checks a limited set of exact contradictions and prepares questions for the next creative task. It does not interpret a manuscript or infer unstated world rules from descriptive prose.

Use the brief before generating, or when an attractive existing name keeps failing for unclear reasons. The output can help a solo writer return to a stalled choice or let collaborators agree on what they are trying to preserve. It is not a factual certificate, an automated editorial judgment or evidence that readers will respond in the intended way. Those claims require work beyond filling out a form.

Describe an action that the name must support

The narrative-action field should say what the person does in the story. A courier signs a public invitation while hiding a family claim gives the naming decision consequences. Mysterious protagonist gives it little to test. The field is retained in the export, but the engine does not read it as a secret command language. If an action implies a rule, enter that rule explicitly in the requirement table.

Period and evidence scope remain unknown when you leave them blank. The page does not assume a contemporary setting, a particular nationality or an English-language naming system. An invented period can be perfectly useful if it is labeled as authored fiction. A real historical claim needs a dated and geographically appropriate source before you describe a candidate as typical or authentic.

Separate the language of the interface from the scope of the evidence. A Japanese interface does not turn a United States source into Japanese birth statistics. Likewise, a fictional port with names written in Latin letters is not automatically a model of any real port community. Use the scope field to state what kind of claim you intend to make and what you have deliberately left unestablished.

Give requirements an authority and a scene

Every row has an ID, kind, value, must/prefer level and scene or check location. Must means the brief treats a condition as mandatory. Prefer means it remains a visible wish that may require a tradeoff. Neither word measures artistic importance for every story; it records your current decision for this one identity.

The supported kinds include an exact fixed name, exact excluded name, exact prefix and minimum or maximum grapheme length. Other kinds record family obligations, a secrecy chapter, reading evidence, cast distinction, prop dependencies or a symbolic association. Those kinds do not all become computable tests. The tool gives each an appropriate check method and routes the relevant ones to a more specific implemented workflow.

The last field matters. Write the opening invitation signature, the shared interrogation scene or the suitcase close-up, rather than simply later. A missing check location becomes an open question. The tool cannot invent the scene where a preference will matter. Its purpose is to make the decision inspectable, not to surround an unsupported adjective with a plausible explanation.

What exact contradiction checks can establish

For one identity, two different mandatory fixed names conflict. A mandatory fixed form also conflicts with an identical mandatory exclusion, a mandatory prefix it does not start with, or a mandatory grapheme interval it violates. Exact comparisons are case-sensitive and preserve the supplied form. An excluded full name does not become a ban on every candidate containing one of its fragments.

Mandatory minimum bounds combine using the largest minimum; maximum bounds use the smallest maximum. A minimum larger than the maximum cannot be solved by generating more candidates. Two mandatory prefixes must be compatible: one must start with the other. The engine checks those typed conditions and reports their actual contradiction, rather than changing a hard requirement to make the page look successful.

The scope is deliberately narrow. The program cannot discover that your invented dynasty requires a forbidden surname merely by reading the narrative-action field. It cannot know whether a symbol would spoil a reveal, whether a family rule is credible, or whether a reference is legally available. Put those obligations into explicit rows and carry them to the scene or evidence workflow that can help you review them.

Use preferences to expose a tradeoff

A preference that conflicts with a mandatory fixed name is reported as a tension. It remains in the brief without blocking the name as though it were a hard rule. For example, a fixed Sela Morrow can coexist with a preferred prefix K, but the result makes the mismatch visible. You can relax the preference or reconsider the fixed decision consciously.

Symbol rows are always labeled creative associations. Calling the returning tide important to the character does not establish that the chosen name historically means tide. A symbol can be written as mandatory if its narrative role is essential, but its claim type remains creative. The appropriate check is a scene that earns the association, not an invented dictionary explanation.

If several preferences compete without an exact fixed candidate, the brief does not pretend to optimize them. It preserves their authority, values and scene tests for a later comparison. This prevents an arbitrary numerical score from making a choice on your behalf. A clear unresolved tradeoff is more useful than a score whose hidden weights merely reflect the order of fields in a form.

Original fictional scene: a signature in the wrong place

Ione wrote three possible names on the back of a ferry timetable. The evening crossing was delayed, and she had promised herself she would choose the courier's name before the boat arrived.

Her favorite candidate carried the family marker she had invented for the ruling house. It sounded right beside the names in the inheritance ledger. It also appeared in the first page's invitation, where the courier signed for a parcel in a crowded hall.

Ione opened the beginning again. The courier spent the next five chapters preventing that same hall from learning whose child she was. A name designed to make the inheritance recognizable would be displayed before the disguise had done any work.

She crossed out the candidate, then wrote it back. The name was not the mistake. The brief was asking it to perform two incompatible jobs at the same moment.

On a clean page she listed what had to survive. The public signature needed to identify the courier without announcing her claim. The family marker needed to connect her to the ledger after the reveal. The final signature needed to express a choice she made herself. Those were three uses of identity, not three reasons to keep drawing another surname.

The boat's arrival bell interrupted her. Across the waiting room, a passenger corrected the name on a ticket without explaining anything about her family. Ione noticed how ordinary the act was. The correction did not have to be a revelation; it could simply establish the reference other people would use.

On board, she rewrote the invitation with the courier's public form. She kept the family marker in the later ledger and added a scene in which the courier chose how to sign after her connection became known. The final image of returning water stayed in the story, but Ione stopped claiming the public name literally meant a tide in a language she had not researched.

By the end of the crossing she had fewer naming decisions left, even though she had not generated another candidate. She knew which form belonged in each scene and what evidence she still lacked. This is an original fictional writing scene. It is not a testimonial, a historical naming example or a claim that a real ferry journey produced a published work.

Why a less revealing name can be the stronger choice

In the scene, making the family connection more obvious would weaken the opening's information boundary. A neutral public form is useful because it lets the courier act before the reader and the hall understand the inheritance. The later family form gains power from arriving at a moment when that connection matters. The two functions require a disclosure plan, not one name with every desired property visible at once.

If Ione kept the royal marker on the invitation, she would need another explanation for the hall's failure to recognize it. That could be a viable story, but it would change the burden of evidence. Perhaps the marker is common, the observers lack access to the ledger or the courier is openly challenging them. Each alternative belongs in the brief as a changed condition rather than a convenient exception introduced at the reveal.

Apply the counterfactual by moving the same name between scenes. Test a public use before the secret, a private use by someone who knows, and a voluntary use after disclosure. Ask what each audience can reasonably infer. The brief records the obligation and recommends the observer workflow; it does not certify that merely entering a reveal chapter has removed spoilers from your manuscript.

Turn each requirement into the next actual task

A family requirement recommends the family planner because inheritance and shared structure need relationships, not another isolated candidate. A secret-until requirement recommends the alias bridge, which evaluates an observer and chapter. A reading requirement recommends the Japanese record ledger only when you explicitly select that kana workflow; another writing system remains an open evidence task. The recommendation is about the decision you requested, not about a genre keyword.

Cast requirements lead to a scene-focused comparison of real full and short forms. Prop requirements lead to occurrence migration so you can inspect what a change does to an inscription or clue. These are suggestions with reasons, not automatic transfers of private story material. The exported brief retains the requirement IDs so you can connect work done elsewhere to the obligation that prompted it.

Some projects need another workflow. Do not force a real-language question into an invented grammar simply because that tool exists. Record the unanswered evidence need, narrow the factual claim, or obtain an appropriate source. A recommendation does not prove demand for a separate page, and an unsupported task does not justify fabricating an answer to keep the workflow moving.

Revise the brief when the story changes

Save the prioritized brief before comparing candidates. When a scene moves or a role changes, update the affected requirement and its test location. A name that was useful under the old brief may remain useful, but it deserves a new review for the new obligation. Do not rewrite the earlier decision as though you always knew the final story.

The download contains narrative action, authored period, evidence scope, ranked requirements, exact conflicts, open questions, preference tensions and recommended workflows. Missing setting fields are null rather than silently contemporary. The shared private project export also retains the inputs for restoration. Review the file before sharing because it can describe hidden identity and reveal plans.

Finish by choosing what evidence would let you accept or reject a candidate. A typed constraint can be checked directly; an emotional effect needs a scene and perhaps reader feedback. Keep those levels separate. The result is a practical agreement about the work a name must do, with unresolved questions visible before an attractive spelling becomes expensive to change.

Does the tool understand my story description?

It preserves your description but does not infer rules from it. Enter obligations as typed requirements. Exact conflicts are checked only within the supported model; a plausible-looking brief does not prove that every narrative contradiction has been found.

Why can a symbol be mandatory but still not factual?

Mandatory describes its priority in your project. Creative association describes the kind of claim. You may require a returning-water motif without claiming a real name historically means tide. Establish factual meanings separately with sources.

What if the period is unknown?

Leave it blank and the export retains null, with an open question. The workbench does not substitute a contemporary period. You can still plan scene functions while withholding unsupported claims about historical frequency or cultural naturalness.

Will this generate the name for me?

No. It prepares the requirements and scene checks that let you judge a later candidate. Use the recommended implemented tools when the task calls for family relationships, observer secrecy, reading records, cast comparison or occurrence-level revision.