Guild Agent
Name Generator

01

Give the alias a desk and a remit

Imagine a visitor entering the guild office with a problem. Which sign directs them to this agent, what question does the agent ask first, and when should the request go elsewhere? Trade dispute, apprenticeship, and missing records supply different portfolios without determining personality.

A working alias might make the portfolio easy to remember while a private register links it to the responsible person. Establish how a visitor can complain about the service without learning unrelated personal details. That arrangement gives the alias a purpose beyond atmosphere.

It also creates a natural opening when an old sign, a transferred portfolio, or a renamed chapter causes a request to reach someone who no longer holds the expected authority.

02

Make the seals equally legible

Two contradictory instructions become interesting when the reader can understand why both appear valid. Perhaps chapters share a charter but interpret a boundary differently, or one handles apprenticeships while another controls funding. Describe each authority in a plain sentence before writing the agent's dilemma.

Avoid a maze of invented ranks whose only function is to make the protagonist seem clever for understanding them. A clerk should be able to explain the immediate conflict, even if the eventual answer requires negotiation. The professional name can then identify the person responsible for clarifying the overlap.

An agent who simply chooses the more convenient seal risks turning ambiguity into personal discretion, with consequences for workers who cannot afford to interpret guild rules so freely.

03

Build the name around a repeated service

A portfolio alias can refer to a form, a meeting place, or a useful habit of explanation. Draft its origin as an event colleagues actually remember. Perhaps Margin Desk began when an apprentice's note exposed a missing provision in the standard agreement.

Decide who proposed the alias and whether the agent likes the association. Keep it distinct from the chapter name and the title of the document central to the plot. Too many similar bureaucratic labels make an otherwise clear scene difficult to follow.

Read the candidate in a visitor's request and a colleague's frustrated complaint. The same call should work when the agent is helpful, mistaken, absent, or required to explain a previous decision.

04

Let records describe work without replacing people

A ledger records selected facts for a purpose. It may establish that a payment occurred without explaining who understood the commission or whether the work was useful. Give the agent an independent conversation with someone affected by the entry.

A tradesperson might recognize the task under a different label, while an apprentice remembers being told it was voluntary. Their accounts can complicate the record without making every document false. Write one case note separating what the ledger proves from what the agent infers.

The portfolio name becomes a promise of a particular kind of attention: reconstructing an agreement through people and records together, rather than treating paperwork as either perfect truth or an obstacle only an unusually daring agent can ignore.

05

Case study: the payment without a commission

Vesen receives two valid chapter instructions about an apprenticeship review. A ledger then shows payment for the same review, although neither chapter admits commissioning it. The apprentice has completed useful work and fears losing recognition if the accounts are reopened.

Write a meeting where the agent states that concern before discussing the unexplained payment. The alias Countermark can suggest the need for a second confirmation without implying suspicion of every participant. The explanation might be an obsolete budget code, a transferred authority, or a task described differently by two offices.

A satisfactory resolution preserves the apprentice's actual contribution while correcting the institutional account, and names which chapter will answer future questions about the resulting credential.

06

Leave a process others can operate

After the case, revise one visible practice: a portfolio notice, a confirmation step, or the wording used when chapters share responsibility. Give a colleague enough information to use the change while the protagonist is away. This prevents bureaucratic competence from existing only as an individual talent that the institution never learns from.

In a campaign, the agent's alias can generate requests from several chapters whose priorities remain distinct. In prose, a final visitor can arrive with an ordinary problem and receive a clearer answer because of the earlier work. The name gains reputation through that modest improvement, including an explicit route for correction when the revised process encounters a circumstance the original case did not anticipate.

07

Revision case: Corcraft and contributor account

Draft setup for Corcraft at the chartered guild network: The person who performed the work explains how local task descriptions differ from the guild ledger terminology. This example uses “Corcraft, Margin” as the proposed public introduction. Failed contributor account version: Corcraft receives “Margin” before anybody addresses this obstacle: Reopening the account threatens an apprentice opportunity even though the disputed work was genuinely completed.

For Corcraft, the apparent achievement therefore exceeds the evidence. In contributor account, the draft treats the title as authority beyond its appointment. Revised contributor account scene: The agent must delay a neat interpretation while hearing details the official forms did not request.

Keep Corcraft's introduction provisional while that cost is paid. The contributor account evidence arrives through an observable detail: The workshop program and payment ledger describe the same date using two apparently unrelated task names. State who appointed the bearer, what service was requested, and which request exceeds that role.

Introduction before revision: “Corcraft, Margin” is announced as settled. After revision: “Corcraft” is used pending the contributor account evidence; “Margin” records only the accepted result. In this guild agent scene, “Kestrelan” takes the other speaking role.

The ending for Corcraft must still acknowledge the local conflict: Two guild chapters issue contradictory instructions under equally valid seals. With contributor account, a limited agreement leaves space for disagreement without making “Margin” meaningless.

08

Revision case: Caltrade and joint chapter instruction

Draft setup for Caltrade at the chartered guild network: Two chapters identify a lead authority and issue one explanation of the shared case responsibilities. This example uses “Caltrade, Countermark” as the proposed public introduction. Failed joint chapter instruction version: Caltrade receives “Countermark” before anybody addresses this obstacle: A valid instruction from each chapter assigns a different person to answer the apprentice next question.

For Caltrade, the apparent achievement therefore exceeds the evidence. In joint chapter instruction, the draft treats the title as authority beyond its appointment. Revised joint chapter instruction scene: Clerks must devote meeting time to an overlap that each chapter previously treated as another office problem.

Keep Caltrade's introduction provisional while that cost is paid. The joint chapter instruction evidence arrives through an observable detail: Both sealed letters quote the same charter paragraph but omit different sentences about shared authority. State who appointed the bearer, what service was requested, and which request exceeds that role.

Introduction before revision: “Caltrade, Countermark” is announced as settled. After revision: “Caltrade” is used pending the joint chapter instruction evidence; “Countermark” records only the accepted result. In this guild agent scene, “Kestrelan” takes the other speaking role.

The ending for Caltrade must still acknowledge the local conflict: Two guild chapters issue contradictory instructions under equally valid seals. With joint chapter instruction, a limited agreement leaves space for disagreement without making “Countermark” meaningless.

09

Revision case: Haltrade and interim credential

Draft setup for Haltrade at the chartered guild network: A clearly limited statement preserves recognition of completed work while the formal review question remains open. This example uses “Haltrade, Bridge” as the proposed public introduction. Failed interim credential version: Haltrade receives “Bridge” before anybody addresses this obstacle: A patron copies the interim statement into publicity without retaining its qualification or scheduled review date.

For Haltrade, the apparent achievement therefore exceeds the evidence. In interim credential, the draft treats the title as authority beyond its appointment. Revised interim credential scene: The guild must explain the credential limits to a workshop that expected an immediately final answer.

Keep Haltrade's introduction provisional while that cost is paid. The interim credential evidence arrives through an observable detail: The temporary certificate names a review meeting absent from the summary sent to the receiving workshop. State who appointed the bearer, what service was requested, and which request exceeds that role.

Introduction before revision: “Haltrade, Bridge” is announced as settled. After revision: “Haltrade” is used pending the interim credential evidence; “Bridge” records only the accepted result. In this guild agent scene, “Kestrelan” takes the other speaking role.

The ending for Haltrade must still acknowledge the local conflict: Two guild chapters issue contradictory instructions under equally valid seals. With interim credential, a limited agreement leaves space for disagreement without making “Bridge” meaningless.