True name & alias

Design what each observer can know

A true name and an alias solve two connected problems: the public identity must work in its setting, and the story must control who can connect it to the hidden identity. Start with those knowledge boundaries. The author knows more than a chapter-one reader. This tool withholds the author-known form unless the selected chapter reaches the reveal point and the observer-knows switch is enabled. Both conditions matter.

A bridge is a creative choice, not proof

Choose no required overlap, a retained initial, or a retained two-letter fragment. Each setting changes how cover forms are constructed. A fragment is a stronger visible cue than an unrelated form, but the tool cannot predict whether your readers will notice it. A similar initial does not establish a shared identity in real life or in a fair mystery. Support the connection through an authored rule, a relationship or a verifiable fictional record.

Keep a useful part fixed

A fixed cover surname survives changes to seed and count. Exclusions and local favorite deduplication can exhaust a finite pool; the tool reports the shortfall instead of breaking the lock. If you need a historically situated biography, independently research the relevant place and period. These component pools are creative constructions, not an evidence-backed reconstruction of a community’s naming practice.

Fictional example: the auction credit

A restorer signs an auction repair note with an inherited workshop credit. A former apprentice recognizes an abbreviation used inside that workshop. Strangers do not have the necessary relationship knowledge. Later, the restorer chooses to disclose the personal identity behind the signature. The clue is fair only if readers have a chance to learn the abbreviation before being expected to understand the recognition.

Change the bridge and the story changes

A conspicuous anagram would let a different observer solve the connection. A completely unrelated cover might require a physical document or an explicit confession instead. Neither choice is inherently deeper. Ask which character should notice, which evidence they possess, and what acting on the discovery costs them. Then check earlier dialogue: a private nickname used in public may reveal more than the carefully designed alias.

Export the right information

The visible-results export contains the observer-scoped result. A saved or exported author project includes input parameters, including the hidden identity. That file is private working material, not a reader-safe cast sheet. Review it before sharing. Moving the reveal chapter does not automatically rewrite your manuscript; it changes this preview and tells you which scenes need another continuity pass.

Build the cover before tuning the resemblance

Write down the public task the alias must perform. A restorer credited on an auction repair note needs a usable professional signature. A stage performer needs an announceable credit. Neither automatically needs the same name as a private family record. This workbench constructs candidate forms; it does not certify a believable historical biography, create documents or establish that a real person can conceal an identity. Keep the use explicitly fictional and supply the setting evidence independently.

Give the character a stable ID before entering either form. The spelling can change while the person remains the same entity. A fixed cover surname protects an already established reference. The visible bridge controls only the declared construction: an initial, a short fragment or no required overlap. No required overlap means the construction does not force a link; it does not guarantee that every letter differs. Inspect accidental similarities when your story needs the two forms to be especially hard to connect.

Use exclusion settings for strings the cover must not contain. If a real-language plausibility rule matters, do not treat an exclusion list as a substitute for research. These small original component pools are intended for creative comparison. Their limits are visible in exhaustion reports. A request for more candidates cannot authorize the tool to break a fixed surname or borrow unverified cultural material.

Work through one observer’s chapter

In the initial example, the author-known name is Aven Reed and the public surname is fixed as Slate. Set the current chapter to four and the earliest reveal to five. In the knowledge table, enter witness | true | 3 and choose witness as the observer. Although this observer has the knowledge, the selected preview still withholds the true identity because the reveal boundary has not been reached. At chapter five, both conditions are satisfied. Change only the observer ID to a stranger and the identity becomes hidden again.

The two conditions represent a deliberately conservative preview contract. They are not a complete model of every narrator or every way fiction can handle dramatic irony. If your scene reveals the truth to readers while keeping characters ignorant, use a separate observer record for that reader state. Do not switch to an all-knowing view and then call its export reader-safe. The selected perspective is part of the result, not a cosmetic label.

Add a clue row such as 2 | signature abbreviation | Q | workshop notation | missing. The clue is visible from chapter two, but the missing knowledge support is flagged. Replace missing with provided only after the story actually teaches or otherwise establishes the necessary convention. This is your editorial declaration, not a fact the tool has verified in the manuscript. The warning concerns what supports the deduction; it does not prevent you from showing an ambiguous detail earlier.

Original fictional scene: a workshop credit

The auctioneer asked the restorer to write her name beneath the repair description. She used the workshop credit, then added a small mark beside the final letter.

“For the varnish?” the auctioneer asked.

“For the joint. The varnish is someone else’s work.”

Near the back of the room, a former apprentice put down his catalogue. He had spent a winter learning that distinction. The mark did not identify a famous family, a secret order or a national custom. It belonged to the little workshop where they had once argued over who deserved credit for an invisible repair.

He approached her during the interval, but did not say the name he remembered.

“They are attributing the whole cabinet to one hand,” he said.

“It will sell more easily that way.”

“And the joint?”

She looked at the catalogue, then at the note she had signed. “The joint should have its own line.”

The auctioneer offered her a pen. Correcting the description would be simple. Signing the correction with her personal name would not. It would connect a public credit to work she had left behind, and to a dispute the apprentice did not yet understand.

“Use the workshop name,” he said.

She made the correction. Beside it, in a smaller hand, she wrote the name under which he had first known her. She folded that corner toward him before returning the page.

When the auction resumed, the public description credited two kinds of work. Only one person in the room had been offered the second identity.

The fictional scene distinguishes recognition, disclosure and publication. The apprentice has a reason to notice the mark. His decision not to use the remembered name gives the restorer control over the next disclosure. The public document changes its attribution without instantly becoming a confession of everything in her past.

Counterfactuals that test the reveal

If the mark were a simple anagram visible to anyone, the apprentice’s special history would do less work. Another bidder might solve the identity, changing the scene from negotiated disclosure to exposure. If the alias were completely unrelated and the mark absent, recognition would need another established cause: a documented technique, a prior conversation or a voluntarily offered clue. Merely stating that he somehow knows would remove the reader’s ability to understand the recognition.

If the apprentice shouted the true name across the room, the same connection would become a violation rather than an invitation. Later characters’ address permissions would change. The name itself would not become more meaningful through extra syllables. Its function comes from who chooses to connect the forms, who hears the connection and which public record preserves it.

Apply this method by making a small knowledge ledger for every decisive identity scene. Record the observable clue, the convention that makes it interpretable, the people with access, and the action taken after recognition. A fair clue need not prove the answer alone. It should support the particular inference the story expects at that point, with alternatives still visible where they remain plausible.

Keep the evidence packet separate from the private project

The observer-safe handoff contains visible candidates, the selected observer and the disclosed clue timeline. It omits the hidden true form when the conditions do not authorize it. A private project, by contrast, stores the author’s inputs. It must contain the true form to restore the decision. Both exports are useful, but they are useful to different audiences.

Before sending a file, inspect the audience named by its button and the chapter included in its data. A production collaborator may need the private project. A beta reader usually needs the bounded identity sheet. A name placed directly in a public clue remains public in that sheet; the tool cannot infer that a string is secret simply because the author meant it to be. Put secrets in the appropriate layer rather than ask an export filter to recognize them by intuition.

Keep a cover-name revision history when a serial already has published episodes. An updated spelling can alter initials, dialogue slips, prop signatures and retrospective summaries. Rerun the observer preview after the change and examine the actual scenes. If the tool produces no eligible candidate, relax one consciously chosen condition, preserve the other locks, and record the reason. A smaller defensible shortlist is more useful than a filled page of names that violate the reveal contract.

Teach the reference before relying on it

A cover identity can remain secret while its public short form still confuses a reader. The optional introduction tables address that narrower problem inside this identity workflow. Enter form ID, display, public/true layer and full/short/label kind, then events with ID, chapter, sequence, observer, action, form, anchor and ambiguity reason. Leave both tables blank if you only need cover generation. Each selected observer has a separate chronological state.

Introduce teaches a full or label form. A short form needs a connected anchor, or an explicit reason to remain intentionally ambiguous. Link teaches how a form connects to an already introduced anchor. Use and recap check that the observer has received that connection; they do not teach it automatically. Unnamed keeps a supplied description with no form ID or anchor, so the engine cannot fill a concealed name into an intentionally nameless entrance. Chapter and sequence values are nonnegative integers, and the same observer cannot have duplicate positions.

For a fictional station scene, introduce ticket17 as Passenger 17 to reader at chapter one, sequence one. A companion can learn nick as Mira in a separate observer sequence. If reader encounters nick before a link to ticket17, the audit reports an unresolved connection. Add a link using ticket17 as its anchor, then a later use records the chapter that taught the referent. Moving the link after the use restores the warning. The companion's earlier knowledge does not solve the reader's missing connection.

True-layer forms remain subject to both the reveal boundary and that observer's knowledge at the event's own time. Learning a secret at chapter six does not authorize it in a chapter-two recap. The handoff omits the concealed display rather than echoing it in a warning. Future events stay outside the current chapter's sheet. These guards concern properly labeled forms; they do not discover secrets an author types into a public label or an ambiguity explanation.

Compare the station scene with one that uses the full concealed name on every appearance. Recognition might become easier, but the intended disguise would disappear. Compare it with no linking exchange at all: the secret survives, yet readers may mistake one traveler for two. The useful revision teaches the public reference without prematurely disclosing the private one. This is why first-use planning is included here rather than counted as another independent generator. The output remains one identity's observer-and-chapter handoff, with connection evidence attached.

Does the tool guarantee a surprising reveal?

No. It constructs declared links and checks the selected knowledge state. Surprise depends on the surrounding story, expectations and clues readers encounter. A weak-looking string link may become obvious beside a signature prop; a strong one may pass unnoticed in a crowded introduction. Test the scene and ask what a reader inferred, not whether the generator promised the alias was subtle.

Why are reveal time and observer knowledge both required?

They represent two different permissions in this conservative preview. A person may know privately before the selected public disclosure point. A reader may be at a later chapter without sharing every character’s knowledge. Model the intended perspective explicitly. If your story uses dramatic irony, use a separate reader observer rather than treating all viewpoints as automatically equivalent once one person knows.

Can I put unrevealed clues in the timeline?

Yes. Future rows remain private planning input and do not appear in an earlier observer handoff. A clue that is already disclosed can still carry an unsupported-knowledge warning. That warning distinguishes seeing a detail from being able to interpret it fairly. Do not mark knowledge provided until the work actually gives the relevant audience a basis for the inference.

Which file can I send to a beta reader?

Use the observer-scoped handoff and inspect its chapter and visible fields. The private project includes hidden input so it can restore the author’s plan. A public clue field also remains public if you type a secret directly into it. No export can infer an unstated secrecy intention. Keep the full private project for collaborators who are authorized to know the complete identity design.