Unit tags & chosen personal names

Ask three questions of the repair slip

A technical tag, a production batch and a chosen personal name can all appear beside one character. They do different work. A namespace and serial can identify one declared unit. A batch can identify several units. A chosen name can express how a person asks to be known without being unique across everyone in a registry. Treating these layers as interchangeable creates errors that another round of name generation will not solve.

This workbench audits an authored registry and the references used in a scene or prop. It checks literal serial rules, duplicate technical pairs, batch ambiguity, scene-scoped name-choice claims and intended-recipient mismatches. It does not generate a robot's personality, verify real consent, certify a manufacturer specification or establish that any real machine is a person.

Use it when a science-fiction story, comic or game needs technical records and personal identity to coexist. The alias workbench answers who knows a concealed identity and which reference can reveal it. This page instead asks what an explicit reference actually selects in a finite registry. A secret name can be perfectly protected while a repair tag still identifies an entire batch rather than the individual needing service.

Keep the serial rule literal

Each namespace has an ID, a literal prefix, an allowed suffix alphabet and minimum/maximum suffix length. Length is counted in Unicode code points after the exact prefix. No regular expression, checksum, real industry convention or inferred manufacturer is hidden in those fields. The default north and south namespaces deliberately share the N- prefix while remaining different scopes.

A unit record has a stable individual ID, namespace, exact serial and batch string or null. Within one namespace, a serial may belong to at most one unit. The same serial in different namespaces can remain valid. North / N-041 and south / N-041 are different technical pairs, even if the visible short tag looks identical on paper.

Serials are not silently trimmed, lowercased or normalized to force a match. An incorrect prefix, suffix length or undeclared symbol is a registry conflict. This catches a missing leading zero or an inserted invisible code point under the authored alphabet. It does not prove that the same string would be valid or invalid in a real production system.

The optional NFC comparison applies only to chosen displays. It never changes a technical key. Keep the distinction explicit: a comparison convention for personal text should not quietly rewrite a serial namespace, and a technical uniqueness rule should not automatically become a social rule that every person must have a different name.

Record what is known about a choice

A choice record includes an ID, unit, inclusive from/to chapters, exact proposed name, claim type and an authored evidence note. A null end leaves the interval open. One unit cannot have overlapping choice records in this model. End an earlier interval before starting another, rather than leaving competing claims for the program to resolve by preference.

Self-reported means the author has entered the record as that person's stated choice. It is still an author-supplied claim, not independently verified consent. Third-party and unknown records retain the proposed wording but do not establish a chosen personal display. If there is no record at the scene point, the result says unknown rather than inventing a personal name from the serial.

A future choice is not applied to an earlier scene. In the default data, the first two units have stated Robin by chapter four. The third unit has no current choice then. At chapter five, a supervisor's proposal becomes visible as an unconfirmed claim; it does not become a self-chosen name just because the proposal includes a plausible personal word.

Use an evidence note to locate the scene, document or creative decision you intend. The note is not an approval certificate. If a character explicitly refuses an imposed label, represent the actual naming decision in your story and records rather than assuming a technical tag gives another character authority to choose for them.

Read the default registry as three individuals

The north namespace contains u1 / N-041 and u2 / N-042, both in batch-7. The south namespace contains u3 / N-041 with unknown batch membership. The two N-041 serials are valid because their namespace scopes differ. The two north individuals independently use Robin. Their shared display is reported as a group of two IDs, without merging them or demanding that either rename.

The repair reference supplies north / batch-7 and says the intended recipient is u2. Its actual candidate set contains u1 and u2. The intended field does not make the ambiguous reference unique. It tells the audit what the writer meant, so the difference between intention and the actual tag remains visible.

The locker reference supplies north / N-042 and resolves to u2. The spoken Robin reference has no namespace scope and selects both current self-reported choices. This is an opportunity to write another distinguishing cue, not proof that the personal names are defective. Characters can clarify a conversation without imposing database-style uniqueness on everyone in the room.

Change the repair reference to serial and provide N-042 in north. Its candidate set becomes u2 while both chosen names remain Robin. That parameter change repairs the actual technical reference. Changing one chosen name would make the spoken call easier to distinguish, but it would not make the original batch-only slip identify a single unit.

Original fictional scene: two name cards at the maintenance desk

Robin placed a handwritten card beside the service terminal. Across the desk, another worker placed a card with the same name. Neither had copied the other. They had submitted the choices on different days, and neither had been told that the word was reserved.

The clerk held up a repair request and said that one card would have to change. The request carried batch-7. Since two workers in that batch were now called Robin, the clerk thought the naming choice had created the uncertainty. The terminal's queue showed one service job, and he wanted one uncomplicated label for its owner.

The second Robin asked whether choosing another word would change the batch printed on the request. The clerk looked down. It would not. Both workers would still belong to batch-7, whatever their cards said. The ambiguity had been on the slip before either personal choice reached the desk.

They checked the individual technical pairs. The request concerned north / N-042, the second worker's record. The clerk added that reference to the service entry instead of crossing out a name card. The first Robin's request remained separate. Nobody had to invent a story in which one worker had borrowed the other's life or had less right to the same chosen word.

At the doorway, a mechanic called Robin and both looked up. This time the uncertainty was ordinary conversation rather than a faulty service record. The mechanic indicated the worker waiting beside the blue tool case and asked how they preferred to distinguish the two names during the shift. The answer could be negotiated there; it did not have to become an immutable serial or a permanent rename.

Both cards stayed on the desk. Each service entry had its own technical pair, and the room had learned to ask for a little more context. The clerk's correction mattered because it repaired the system that needed precision without treating a person's introduction as the mistake.

This is an original fictional scene. It reports no real manufacturer, conscious machine or consent procedure. The names affect agency and a working relationship. A story that replaced one Robin with a different personal name could make the call simpler while leaving the batch-only request just as ambiguous.

Resolve the supplied reference, not the writer's intention

A reference declares its kind: serial, batch or chosen-name. A serial reference requires a namespace. Batch and chosen-name references may use an optional namespace scope or search the whole supplied registry. The tool does not infer a kind from what the text resembles. A value that happens to be Robin in a serial field is not rescued by searching the personal names instead.

The result distinguishes invalid serial format, an unknown reference, multiple candidates and one candidate that disagrees with the intended unit. A well-formed N-099 can be unknown because it has no record. A malformed personal word in the serial field is invalid-format. Neither outcome invents the intended recipient as a successful technical match.

The intended unit is a comparison target, not an extra identifying clue. If a slip actually selects u1 while the author intended u2, the output preserves u1 as the actual candidate and marks the mismatch. Otherwise the audit would merely restate the writer's intention and hide the production problem it was supposed to find.

Batch or chosen-name resolution is confined to the supplied scope. A batch with one entered member can appear unique today and become ambiguous after another record is added. The registry does not certify worldwide uniqueness or physical presence in a room. Include the relevant records for the creative question you are checking, and keep that scope with the handoff.

Decide which layer the scene needs

A maintenance form may need a technical pair. A conversation may need a personal name plus context. A public introduction may deliberately omit production metadata. The workbench does not decide that a serial should replace every social reference merely because it is an exact key inside the supplied model.

Likewise, preserving a serial does not require a character to accept it as their personal name. The output retains the technical record and the stated choice separately. That lets a writer show continuity in a prop while changing the way people address the character. Use the relationship-address tool if the scene also needs directional permission about who may use a particular form.

If two chosen names match under NFC, their raw spellings still remain separate in the records. The comparison can expose an ambiguous reference without rewriting either display. It does not establish cultural equivalence or declare one spelling a mistake. Review the actual forms and the scene's reference needs rather than treating a normalized comparison key as the only legitimate presentation.

An authored personal choice can also remain unknown. That is not a prompt to fill the page with an attractive generated replacement. A technical registry can be usable before the character has made a naming decision. Let the absence remain an explicit story question when that uncertainty belongs to the character's development.

Carry the scope and the limitations with the audit

The dedicated handoff is a private author audit. It includes exact technical records, current choice claims and the reference candidate sets. Project exports retain all input, including future choices and evidence notes. This page does not provide observer-safe secrecy controls or a public identity sheet. Prepare a separate public document if a technical identifier or unconfirmed proposal should remain hidden.

The local model accepts thirty namespaces, one hundred and twenty individuals, two hundred and forty choice records and two hundred and forty references. Namespace suffixes use one to forty code points. A batch of examples is not a population study, and a successful reference is not proof of a real identity, legal permission or external system compatibility.

The scene chapter selects naming intervals. It does not simulate creation, retirement, physical location or life status for every unit. All entered units remain in the declared technical registry scope. If a story question depends on who is present or operational, establish that scope and evidence separately rather than reading it into a name match.

Save the project before revising a namespace, tag or choice record. Rerun the actual prop references afterward. The strongest result is a scene that gives the person an intentional form of introduction and gives a technical process exactly the specificity it needs, with neither layer pretending to do the other's work.

Must two people with the same chosen name rename?

No. The registry preserves their individual IDs. A spoken reference may need another cue, while a technical process can use the exact namespace and serial. The tool does not turn key uniqueness into a rule for personal identity.

Does self-reported mean consent was verified?

It is the claim type entered by the author, with an evidence note. The software cannot verify a fictional scene or a real person’s consent. Third-party and unknown records are not promoted into established choices.

Why does an intended recipient not solve an ambiguous tag?

The intended field records what the writer meant. Actual candidates come from the declared reference. Using intention to choose a recipient would hide the difference between a precise prop and an ambiguous one.

Can the audit be shared as a spoiler-safe identity sheet?

No. It is a private author record and can expose technical data and unconfirmed proposals. Projects contain future input too. Prepare and review a separate public sheet for an audience that should not see those details.