Oracle
Name Generator

01

Witnessing has its own vocabulary

Name the experience before naming the person who receives it. A mirror witness might observe arrangements of objects; a dream witness might retain an impossible conversation; a horizon witness might see several outcomes occupying the same distant street. Choose one recognizable form and decide what its observers call the first raw account.

An oracle title can incorporate that term, perhaps alongside the place where a reliable witness first recorded the experience. Keep the personal name available for ordinary scenes. Someone who receives visions still orders lunch, misplaces correspondence, and has relationships that do not concern prophecy.

A ceremonial introduction should therefore identify a role without pretending that every remark the person makes is an inspired message.

02

Three stages of a prediction

Keep the original vision distinct from its transcription and its interpretation. An oracle sees a red chair beside a window; a recorder writes a royal seat beneath an opening; a council concludes that a ruler will leave the palace. Each stage introduces choices.

The original perception may also omit context, so precision does not make the interpretation certain. Give the oracle a habit of preserving small details that seem unimportant at first. A mundane object can later distinguish a metaphor from a literal setting.

Readers should be able to revisit the account and understand how a mistaken conclusion arose. Ambiguity becomes productive when several interpretations fit the available evidence, rather than when the author changes the vision's contents after the reveal.

03

The audience changes the future

Decide whether a vision reports an unavoidable event, one conditional future, or an image with no direct predictive force. A possible future is especially useful when announcing it changes people's behavior. A council that hears a warning about an empty granary may move grain too early, producing the shortage it feared.

The oracle then faces a communication problem rather than a contest of supernatural strength. Who needs to know, how much context can be shared, and what actions remain reversible? Avoid making silence automatically wise or disclosure automatically reckless.

Both can have costs. Let affected people question the oracle's framing, especially when a public title lends a speculative interpretation more institutional weight than its evidence supports.

04

An honest limitation

Give the gift an absence that matters. A vision might contain no audible words, show only a room's arrangement, or fail to distinguish a model from a full-sized place. The oracle should know some limitations through previous errors.

Record an instance where the same image meant something ordinary, preventing every symbol from having a fixed universal meaning. A bowl need not always represent hunger, and a closed door need not always mean refusal. Ordinary inquiry remains useful: visiting the room, interviewing a carpenter, or checking a meeting notice can narrow possibilities.

Present the supernatural mechanism as fiction, and do not suggest that a character's method predicts real events or justifies advice about actual health, money, or personal decisions.

05

The meeting not yet accepted

Write an oracle scene beginning with a reflection of a room prepared for a gathering that nobody has scheduled. Describe five objects without explaining them. Next write two invitations that could plausibly produce that arrangement for different reasons.

Have the oracle choose one concrete question to ask before sharing the vision publicly. Then draft the same scene after someone has circulated a careless summary. What new pressures appear, and which choices remain available?

Use the formal title in the circulated announcement and the personal name when a friend asks whether the oracle wants to attend. The contrast should reveal the distance between an institution's confident presentation and the person's more careful account of what was actually seen.

06

Responsibility after an error

A mistaken interpretation should leave something to repair. An oracle may need to correct a public record, help reverse a precaution, or acknowledge someone whose objection was dismissed. The gift itself need not vanish to make that repair significant.

Decide whether the witness houses distinguish accurate reporting from successful prediction; rewarding only dramatic outcomes will encourage overstatement. A useful naming tradition might commemorate a carefully corrected account instead of a celebrated prophecy. Before settling on the name, write a brief correction signed by the oracle and a friendly reply from someone who remains skeptical.

If both sound credible, the identity can support an ongoing character rather than a device that appears only to deliver enigmatic plot instructions.

07

Revision case: Vaerision and double account

Draft setup for Vaerision at the witness houses: Preserve two independent descriptions of one vision without allowing either recorder to see the other. This example uses “Vaerision, Account” as the proposed public introduction. Failed double account version: Vaerision receives “Account” before anybody addresses this obstacle: The accounts differ because one recorder replaced unfamiliar objects with more prestigious ceremonial equivalents.

For Vaerision, the apparent achievement therefore exceeds the evidence. In double account, the draft turns one bounded effect into an unlimited solution. Revised double account scene: Comparing the accounts delays public interpretation until both recorders have finished and signed their observations.

Keep Vaerision's introduction provisional while that cost is paid. The double account evidence arrives through an observable detail: A homely stool appears in one version where the other confidently names a vacant throne. Write one observable effect, reserve its cost, and leave the disputed claim outside the result.

Introduction before revision: “Vaerision, Account” is announced as settled. After revision: “Vaerision” is used pending the double account evidence; “Account” records only the accepted result. In this oracle scene, “Oraviel” takes the other speaking role.

The ending for Vaerision must still acknowledge the local conflict: A prediction becomes likely only because people act on a careless paraphrase. With double account, a limited agreement leaves space for disagreement without making “Account” meaningless.

08

Revision case: Calmireth and context window

Draft setup for Calmireth at the witness houses: Retain one otherwise overlooked peripheral object from a vision for later comparison with ordinary evidence. This example uses “Calmireth, Window” as the proposed public introduction. Failed context window version: Calmireth receives “Window” before anybody addresses this obstacle: A copied stage prop resembles the object and sends investigators toward the wrong gathering.

For Calmireth, the apparent achievement therefore exceeds the evidence. In context window, the draft turns one bounded effect into an unlimited solution. Revised context window scene: Selecting the peripheral object prevents preserving the central image with equal visual detail afterward.

Keep Calmireth's introduction provisional while that cost is paid. The context window evidence arrives through an observable detail: The remembered object bears a repair patch absent from the polished replica shown publicly. Write one observable effect, reserve its cost, and leave the disputed claim outside the result.

Introduction before revision: “Calmireth, Window” is announced as settled. After revision: “Calmireth” is used pending the context window evidence; “Window” records only the accepted result. In this oracle scene, “Oraviel” takes the other speaking role.

The ending for Calmireth must still acknowledge the local conflict: A prediction becomes likely only because people act on a careless paraphrase. With context window, a limited agreement leaves space for disagreement without making “Window” meaningless.

09

Revision case: Symbel and revision cord

Draft setup for Symbel at the witness houses: Display which published interpretation was current when a reader first received the oracle account. This example uses “Symbel, Revision” as the proposed public introduction. Failed revision cord version: Symbel receives “Revision” before anybody addresses this obstacle: A council cites an obsolete confident summary while hiding the later notice that qualified it.

For Symbel, the apparent achievement therefore exceeds the evidence. In revision cord, the draft turns one bounded effect into an unlimited solution. Revised revision cord scene: Every correction must remain publicly attached, allowing readers to compare rather than erase earlier claims.

Keep Symbel's introduction provisional while that cost is paid. The revision cord evidence arrives through an observable detail: The cord shows an earlier publication knot than the one visible on the council wall. Write one observable effect, reserve its cost, and leave the disputed claim outside the result.

Introduction before revision: “Symbel, Revision” is announced as settled. After revision: “Symbel” is used pending the revision cord evidence; “Revision” records only the accepted result. In this oracle scene, “Oraviel” takes the other speaking role.

The ending for Symbel must still acknowledge the local conflict: A prediction becomes likely only because people act on a careless paraphrase. With revision cord, a limited agreement leaves space for disagreement without making “Revision” meaningless.