Warlock
Name Generator

01

Two parties, several names

Give the practitioner an ordinary name before creating the covenant title. The public form may advertise an authorized task, while the patron uses a precise designation linked to a particular agreement. Keep those contexts legible.

A traveler who knows the title should not thereby gain access to a private identity or command the warlock. Similarly, the patron's name may identify an office rather than an individual: a star envoy can retire, leaving a successor bound by the same clauses. Decide whether the signature records the human signer's intention, the words spoken aloud, or an independently witnessed version.

This choice determines what a naming dispute can change and prevents titles from becoming unlimited magical permissions.

02

A benefit worth bargaining for

Specify the service received in practical terms. An archive spirit could retrieve an indexed memory from a collection the warlock cannot physically enter. A star envoy might lend a route between two observed lights.

An ancient grove could recognize promises spoken beneath one particular canopy. None needs to grant every useful ability. The warlock should have a reason for choosing this benefit over ordinary alternatives, and the patron should receive something it cannot easily obtain itself.

That exchange supports conflict without requiring either party to be foolish or secretly malicious. The patron may be sincere and still misunderstand what a human workday, friendship, or seasonal obligation demands from the person doing its errands.

03

Terms that survive a scene

Write three clauses before drafting a dramatic bargain: the promised task, the limit on demands, and the exit process. A clause that says provide assistance is too vague unless vagueness is itself an acknowledged risk. Prefer a countable delivery, a defined collection, or a period with a clear ending.

Include a procedure for disputes that does not depend solely on the stronger party's opinion. A neutral registry, a copied receipt, or a witness whose interests differ from both signers can make negotiation playable. The covenant title might preserve the name of that witness or the location where terms were accepted, giving the generated identity a connection to institutional memory rather than simple intimidation.

04

Consequences without arbitrary punishment

A meaningful cost should follow the agreed benefit. Borrowing an archive memory may require contributing an equally well documented observation; using a stellar route may close another scheduled passage; invoking a grove's witness may require returning to hear a competing account. These costs create decisions.

Avoid surprise clauses invented only after a solution becomes convenient. A patron can conceal information, but readers need evidence that concealment is possible and a way for the character to investigate it. The warlock should be able to decline a request within established conditions.

An exit that costs a useful privilege is often more interesting than a pact that cannot be challenged under any circumstances and therefore removes meaningful negotiation.

05

The new footnote exercise

Write a contract page in plain language and keep it under one hundred words. Then add a footnote in the practitioner's handwriting that neither signer remembers approving. Draft the first conversation about it with both parties assuming the other has acted in good faith.

Include a concrete consequence, such as a delayed delivery or a closed reading room, so the dispute is more than wordplay. The warlock must propose a test capable of proving their own interpretation wrong. Use the covenant name when invoking authority and the personal name when asking for trust.

The difference should reveal how the same person occupies a professional role without being reduced to it.

06

A pact with an afterlife

Consider what happens when the task is completed. Does the title retire, remain as a historical distinction, or pass to another willing signer? The practitioner may keep friendships made through the covenant after its powers end.

A patron might owe a final receipt that protects the former warlock from future demands made in its name. Record where copies live and who can explain the terms to outsiders. Before finalizing a generated name, write a scene in which the warlock introduces themselves after leaving the agreement.

If the identity collapses without the patron, add a personal ambition, household connection, or independent craft. The bargain should shape a life that continues beyond its expiration.

07

Revision case: Veskoran and split seal

Draft setup for Veskoran at the covenant registry: Compare two covenant copies and illuminate the earliest sentence on which their wording differs. This example uses “Veskoran, Seal” as the proposed public introduction. Failed split seal version: Veskoran receives “Seal” before anybody addresses this obstacle: A legitimate amendment appears on only one copy because the registry never acknowledged its messenger.

For Veskoran, the apparent achievement therefore exceeds the evidence. In split seal, the draft turns one bounded effect into an unlimited solution. Revised split seal scene: Both holders must willingly present their copies, and the comparison temporarily suspends disputed privileges.

Keep Veskoran's introduction provisional while that cost is paid. The split seal evidence arrives through an observable detail: The glowing discrepancy begins beside a delivery date recorded before the new clause was negotiated. Write one observable effect, reserve its cost, and leave the disputed claim outside the result.

Introduction before revision: “Veskoran, Seal” is announced as settled. After revision: “Veskoran” is used pending the split seal evidence; “Seal” records only the accepted result. In this warlock scene, “Korevran” takes the other speaking role.

The ending for Veskoran must still acknowledge the local conflict: A patron fulfills the letter of a generous bargain while revealing an unexpected limitation. With split seal, a limited agreement leaves space for disagreement without making “Seal” meaningless.

08

Revision case: Eshavar and echo receipt

Draft setup for Eshavar at the covenant registry: Replay the precise acceptance spoken when a completed covenant task was formally acknowledged. This example uses “Eshavar, Receipt” as the proposed public introduction. Failed echo receipt version: Eshavar receives “Receipt” before anybody addresses this obstacle: A patron office changes hands and the successor disputes whether its predecessor accepted final completion.

For Eshavar, the apparent achievement therefore exceeds the evidence. In echo receipt, the draft turns one bounded effect into an unlimited solution. Revised echo receipt scene: The receipt preserves only one acceptance and cannot record private conversation surrounding the exchange.

Keep Eshavar's introduction provisional while that cost is paid. The echo receipt evidence arrives through an observable detail: The replay includes the title of an office later removed from the institutional register. Write one observable effect, reserve its cost, and leave the disputed claim outside the result.

Introduction before revision: “Eshavar, Receipt” is announced as settled. After revision: “Eshavar” is used pending the echo receipt evidence; “Receipt” records only the accepted result. In this warlock scene, “Korevran” takes the other speaking role.

The ending for Eshavar must still acknowledge the local conflict: A patron fulfills the letter of a generous bargain while revealing an unexpected limitation. With echo receipt, a limited agreement leaves space for disagreement without making “Receipt” meaningless.

09

Revision case: Orvelith and witness ribbon

Draft setup for Orvelith at the covenant registry: Show which independently registered witness last examined the clause currently invoked by either signer. This example uses “Orvelith, Ribbon” as the proposed public introduction. Failed witness ribbon version: Orvelith receives “Ribbon” before anybody addresses this obstacle: A retired witness asks for release while both signers still depend on their interpretation.

For Orvelith, the apparent achievement therefore exceeds the evidence. In witness ribbon, the draft turns one bounded effect into an unlimited solution. Revised witness ribbon scene: Requesting a new witness reading opens the same clause to challenge by the other party.

Keep Orvelith's introduction provisional while that cost is paid. The witness ribbon evidence arrives through an observable detail: One knot points to a registry desk whose appointment book lists an unannounced retirement. Write one observable effect, reserve its cost, and leave the disputed claim outside the result.

Introduction before revision: “Orvelith, Ribbon” is announced as settled. After revision: “Orvelith” is used pending the witness ribbon evidence; “Ribbon” records only the accepted result. In this warlock scene, “Korevran” takes the other speaking role.

The ending for Orvelith must still acknowledge the local conflict: A patron fulfills the letter of a generous bargain while revealing an unexpected limitation. With witness ribbon, a limited agreement leaves space for disagreement without making “Ribbon” meaningless.