Voice Reference: Oath-Bound Content System

This document is a candidate for splitting into three dedicated files: (1) Construction and Phrasing Reference, (2) Prohibited and Controlled Vocabulary, and (3) Terminology and Naming Reference. The split is planned but not yet scheduled. Until it happens, this document remains the single authoritative voice reference. See -to-do.adoc for the planned structure.

The World in Brief — Oath and Obligation

In most places, a person’s word matters because other people remember it. Reputation travels, trust builds or breaks, and a man who behaves poorly or speaks rashly finds doors closing to him. That is familiar ground. What is different in Oath-Bound is that a spoken promise is not only remembered — it is almost tangible.

When someone gives their word here, they are not just stating intent. They are fixing a line that others can see, measure against, and act upon. Even the simplest promise begins to shape expectations: who can rely on you, who can challenge you, and what others are entitled to assume you will do. People listen closely, not only to what is said but to what is left unsaid, because both begin to carry weight once spoken aloud. And they watch what you do — because in a world where words carry this kind of weight, deeds are the evidence against which words are tested. A man who speaks well and acts poorly is understood to be something specific, and that understanding travels.

For the most part, a promise made in Oath-Bound carries no more intrinsic force than it would anywhere else. What makes the difference is cultural: most people here understand, at some level, that a promise is a small oath, and everyone knows that oaths have consequences. This awareness shapes how commitments are made, how they are heard, and how seriously their breach is taken. A warlord’s oath to his liege, a merchant’s bond to his trading partner, a sworn declaration before witnesses — these are real and binding in every practical sense, enforced through memory, reputation, and the social consequences of breaking what was given freely. The gods are not involved, and do not need to be.

Some oaths, however, are something more than social arrangements. What people build between themselves can reflect something that exists beyond them — a structure of obligation that runs through the world at every level. The old formulation captures it precisely: as above, so below. The laws that govern oaths among mortals are not an approximation of divine law — they are the same law, differently expressed.

A Bound Oath is one that has been recognized and answered for by the gods themselves. The god becomes a party to the commitment, and what is fixed between the people present is fixed in something larger than either of them. How this happens varies: in more settled societies, a priest mediates the process through formal ritual, ensuring the oath is properly framed and the divine attention properly engaged. In older or less formal traditions, the same end is approached differently — through spectacle, ceremony, and the presence of witnesses enough to make the moment undeniable, often with some object serving as a focus for what is being sworn. Whether such objects accrue significance of their own over time is a matter on which reasonable people in Oath-Bound disagree, though the families and clans that keep them tend to treat the question as settled.

Bound Oaths have shaped the history within which the players live, and the consequences are not difficult to read. About 650 years ago, a group of exiles bound itself with what was probably the first fully mediated Bound Oath in recorded history — a commitment to carve out a new homeland and to govern it in a manner worthy of what had been sworn. The Empire that followed stood for three centuries. The oath was broken. The Empire fell 353 years ago — the campaign present is 353 NA — and the world the players move through is still, in many respects, living inside that consequence. The ruins are present and obvious. The successor states have memories, and the people have memories that are not old enough to have become legends. Even the lowest serf in the most remote corner of Oath-Bound understands on some level that the gods took notice when that oath was made — and that they noticed when it was broken.

For you as a player, most of what you encounter will be obligation of the ordinary kind — promises, debts, sworn loyalties, and the reputational consequences of how you handle them. But Bound Oaths exist, some of them still active, and the circumstances that lead to them are not always formal or anticipated. Understanding that there is a difference between a commitment witnessed by people and one witnessed by something that does not forget is, in Oath-Bound, considered basic literacy.


Campaign Present — Chronological Anchor

The campaign present is 353 NA (656 AF). The Fall of the Velasian Empire occurred 353 years ago. No living person has unmediated memory of the Empire. Family traditions that claim to trace back to imperial service are eight to ten generations removed from the events they describe.

Use this anchor when writing content that references elapsed time:

  • "over 650 years ago" — the Foundation Oath and Velasian landfall

  • "three centuries" or "300 years" — the span of the Empire (0–303 AF)

  • "353 years ago" — the Fall (303 AF / 0 NA)

  • "over 300 years" — the post-imperial period to campaign present

Player characters are typically in their twenties to mid-forties, born in the 307–352 NA range. They are approximately 16 generations removed from the Fall.


Site Registers

This work generates content for four sites with distinct audiences. Apply the correct register to every document before drafting.

PUBLIC and PLAY

Audience: players and potential players, including those unfamiliar with AD&D.

Style: informative but somewhat informal. Modern analogies are acceptable and sometimes preferable to obscure period equivalents. Setting-appropriate analogies are preferred when they work as well. AD&D terminology explained on first use or avoided where a plain equivalent serves.

DMG — GM Bible

Audience: game masters and world designers.

Style: grammatically precise. Complexity is permitted where the subject demands it. Unnecessary complexity — vague abstractions, words that perform precision without delivering it — is not. The reader is assumed to be intelligent and capable of interpretation.

Two content types exist within DMG: rules (portable across systems) and lore (specific to the Oath-Bound campaign and rule set). Keep these distinct within documents and across the nav structure. They have distinct registers within the GM Bible frame:

Rules register

Precise, formal, no anachronism. The text describes mechanics, procedures, and design decisions. No modern-world analogies — these import connotations that the rules text cannot control and that can mislead players or referees about how the system works. Game-associated comparisons are acceptable where they aid mechanical clarity. No informal asides. No humor. No rhetorical digressions.

If a rules passage contains a modern analogy, a conversational aside, or an informal example unconnected to gameplay, flag it — that is register drift and should be corrected.

Lore register

More conversational than rules. Analogies and examples are permitted where they genuinely illuminate the material for a referee who needs to understand and run it. Modern analogies are acceptable at editorial discretion where no period equivalent carries the same clarity. Illustrative digressions are permitted — including meme-type images and asides in exhibit documents where they suit the document’s character. The tone may be warmer and the voice more discursive than rules register allows.

Lore register does not mean informal without purpose. The conversational latitude exists to serve comprehension, not to substitute for it.

UO — Campaign Site

Audience: players in the Under Oath campaign.

Style: period-appropriate without faux-medieval affectation. Modernisms avoided. The reader is immersed in the world and the content should feel native to it.


Writing Quality Standards

These apply across all sites unless a specific site register overrides.

  • No paired or tripled short sentences used for rhetorical emphasis.

  • During final polish passes, review section closings for dyadic short sentences — two consecutive short sentences used for tension or emphasis. Where the rhythm isn’t genuinely doing work, elide them into a single sentence using conjunctions (and, but, or) to maintain the tension while improving flow. Example: "That’s not comfortable. It’s not meant to be." → "That’s not comfortable, and it’s not meant to be." The stacked form should survive only where the pause between sentences does specific work.

  • Mid-paragraph staccato rule — the same paired-sentence problem occurs throughout body paragraphs, not just at section closings, and is one of the most recognizable AI writing artifacts. Pairs or triplets of short declarative sentences used to build emphasis mid-paragraph — "The structure is present. The honesty is not." / "That is a different dynamic. It has a different objective." — should be collapsed using conjunctions or subjunctive constructions rather than left as separate sentences. This is not purely a cosmetic fix: joining adjacent sentences forces the relationship between the ideas to be made explicit, which associates them into a single context rather than merely placing them adjacent. "The structure is present. The honesty is not." states two facts. "The structure is present even when the honesty is not" states a relationship and does more work in the same space.

Subjunctive constructions are particularly useful because they can subordinate a condition, concession, or consequence into the main clause without adding length — "a session worth having for most of the people at the table, even where not for all of them" does more work than two sentences would. Chained conjunctions are similarly acceptable where multiple related ideas need to be held together: and, but, or, while, even where, even when, whether or not, and similar.

Apply this test to every paragraph during any polish pass. The default is conjunction or subordination; the staccato form must justify itself by the specific work the pause is doing.

  • No staccato "Not A but B" constructs used as a stylistic default.

  • No conclusory restatement at the end of sections — absorbed into the argument or cut.

  • Commentary pieces should include humanizing digressions where the material invites them.

  • "Survive" rather than "endure" where the consequences are explicitly fatal — this is a game with real character consequences.

  • Imprecision words — the slop list — a category of words that describe the writer’s intended effect on the reader rather than the thing the prose is actually describing. They are placeholders that feel like content. The test: does this word describe what is actually happening, or does it describe how the writer hopes the reader receives it? If the latter, replace it.

The standing prohibited list:

  • lands — describes hoped-for reader reception, not the argument itself. Replace with what the argument actually does: "makes the point", "establishes", "clarifies", "confirms", or restructure the sentence so the argument speaks for itself without the closure.

  • holds (in the sense of persists, remains true, or applies) — vague persistence verb. Replace with what specifically is true or persisting: "remains", "applies", "continues to shape", "governs", or state the specific claim directly.

  • gives (in the sense of provides, produces, or enables) — papers over the actual relationship. Replace with the precise verb: "produces", "enables", "reveals", "creates", "establishes", depending on what the transaction actually is.

  • sits (in the sense of exists, belongs, or occupies a position) — spatial metaphor applied to abstractions. Replace with the actual relationship: "belongs", "operates", "functions", "exists", "applies".

  • carries (in the sense of contains, implies, or bears weight) — as above. Replace with the precise relationship.

  • works (in the sense of functions, succeeds, or applies) — circular and vague. State what specifically functions or succeeds and why.

  • generative — performs precision without delivering it. Remove or replace with what is actually being produced.

  • nuanced — almost always a signal that the writer has not done the work of describing the nuance. State the nuance directly or cut the word.

  • tapestry, delve, unpack — AI slop markers. Remove on sight.

  • earned — vague and conclusory in most contexts. Use only for exchange of services for payment ("wages earned"), or behavior that produces a specific, nameable, tangible benefit ("earned a commission"). The phrase "trust earned incrementally" is borderline acceptable in contemporary usage where trust accruing through repeated reliable conduct is the concrete outcome; pass at editorial discretion. Outside these contexts replace with the specific verb: accumulated, built, demonstrated, acquired, decided, produced. The test: is there an actual transaction, a concrete named outcome, or a well-established idiomatic use? If not, replace.

  • hollow sentence closures that gesture at meaning without delivering it: "That is what this is about", "This is the point", "That is what matters here" — name what the surrounding prose has already shown, adding nothing. Cut or absorb into the argument.

The standing list is not exhaustive. Any word that describes effect rather than mechanism, or gestures at a claim without making it, is a candidate for replacement, whether or not it appears above.

The diagnostic test applies on every polish pass, including to words not on the standing list. When a word from the slop category is caught in output — by the author or by review — it is added to the list with its context and a confirmed replacement, so the list grows from real examples rather than theoretical ones. Iteration is the method: apply the test, catch the instance, add the entry, tighten the list.

The rationale for this iterative approach is worth stating explicitly. As the corpus becomes more precise, imprecision becomes more visible — a vague word that might pass unnoticed in undifferentiated prose stands out as an island against a surrounding baseline of specific, precise language. The more rigorously the diagnostic is applied, the more obvious each remaining lapse becomes, and the more reliably such lapses function as indicia of AI output rather than authorial choice. Precision compounds: every pass raises the standard against which the next pass is measured.

Content that is identifiably AI in origin is acceptable. Content recognizable as AI slop is not, and the diagnostic test is the primary instrument for telling them apart.

  • Telegraphing — announcing what is about to be said rather than saying it. The writer signals the punch instead of throwing it. Common forms: "it is worth noting", "it is worth stating", "it is worth being direct about", "one thing to observe is", "it should be acknowledged that", "the point here is that", and variants. These defer the actual content by one clause and add the appearance of considered judgment without delivering it.

Telegraphing survives only where the point being flagged is genuinely counterintuitive, where the reader might otherwise skim past it, or where the writer is explicitly stepping outside the main argument and the signal is load-bearing. The test: would removing the telegraphing phrase change what the sentence means or how the reader receives it? If not, remove it and let the sentence lead with its content.

"Telegraphing" is the standing term for this category across all Oath-Bound corpus directives.

  • Declarative pivot rule — Avoid sentences that name what the surrounding prose has already shown. Sentences that state the author’s conclusion — "They are the world", "This is the cost", "That is what matters" — typically do less work than they appear to and frequently dilute the point they’re meant to emphasize. Trust the evidence. Cut the label.

  • Complexity and readability — Complexity is justified by precision, not by register. If a simpler word carries the same meaning, use it. If it doesn’t, the complex word stays without apology.

  • Glossary italics convention — All glossary terms are italicized on first use within any document. Per-section judgment is permitted in long referee-facing documents. Applies to both world-specific coinages and technical terms retained for precision. The glossary serves as the canonical "do not simplify" registry for retained technical terms.

  • Orientation documents describe frames, not procedures. When referencing a rules system in an orientation or foundation document, describe what the actor is navigating and what is at stake. Do not replicate procedural detail. Procedure has a home in Rules; the orientation document points toward it without substituting for it. The test: could this paragraph be lifted into the relevant Rules page without loss? If yes, it belongs there, not here.


Standard Rulings

These rulings apply to all new content and to documents being actively worked on in the current session. They are not applied retroactively to uploaded corpus documents during normal working sessions — back-fixes to existing documents are handled as dedicated cleanup passes.

When a non-conforming term appears in an uploaded document that is being used as source material, note the discrepancy internally and apply the correct form in any output derived from it. Do not interrupt the working session to correct the source document unless a cleanup pass has been explicitly requested.

These rulings exist because the same errors recur across sessions and the cost of propagating them through the corpus is high.

American English

All corpus content is in American English. British spellings are non-conforming and should be corrected on any active editing pass. Common examples: -ize not -ise; recognize, emphasize, organize; color not colour; rumor not rumour; favor not favour. Do not introduce new British spellings in authored content.

Confirmed people and culture names

Use these forms exclusively. Do not introduce variant spellings without a formal naming decision recorded in meta/.

Correct form Retired forms Notes

Velasian

Velarian

The people and the culture. Valasia is the empire name.

Valasia

Valeria

The empire name.

Skeld / Skelds / Skeldic

Skand / Skands / Skandic

The people and their adjective form.

Skald / Skalds

Skeld saga-speaking poets and storytellers. Distinct from Skeld (the people). Never conflate. Visual check required on any find-and-replace involving either term.

Cwym

Welsh-analogue Hillfolk family.

Bryt

Hen Ogledd / Welsh-border Briton analogue Hillfolk family.

Celt

Pre-Viking Dal Riada (Dalradian) analogue Hillfolk family.

Hillfolk

Hellfolk

Velasian administrative coinage for the Cwym/Bryt/Celt grouping. Used ironically by the peoples it describes.

Markish

The common folk majority population.

New Velasians

Surviving enclave communities of Velasian-descended culture.

Felafoy

The Steady Lands

The colloquial name for Velaþoiāän, the archaic Velasian outpost. Corruption of the original through oral transmission and poor literacy.

Retired terminology

These terms have been superseded. Flag any occurrence in new or reviewed documents and replace with the confirmed form.

Retired term Confirmed replacement

flash-binding

Open Call

flash-bind

Open Call

Velarian

Velasian

Valeria

Valasia

Skand / Skands

Skeld / Skelds

Hellfolk

Hillfolk

The Steady Lands

The Felafoy

Roles Before Rolls

Roles and Rulings Ahead of Rolls

Book of Value

Book of Values

Catalogue

Catalog

power-bands.adoc

miracle-bands.adoc (superseded)

roles-before-rolls.adoc

roles-rules-rolls.adoc (renamed)

Session Retro

Session Journal

B/C/M (Master)

BCF (Basic/Competent/Fluent)

Prime Requisite

excluded from corpus — do not use

Innate/Binary (competency types)

Advanceable/Fixed

Arcane practitioner terminology — register stack

The terminology for informal arcane practitioners varies by register. Apply the correct term for the target audience and context.

Term Usage

adept

Self-designation used by rustic adepts among themselves. Modest, non-specific. Claims skill without claiming magic. Never challenge or replace this with another term in content written from the practitioner’s perspective.

wise-woman, canny man, and similar

Community-level circumlocution. What the people who rely on a rustic adept call them. Deliberately ordinary. Use in UO and player-facing content to convey social texture.

rustic adept

The formal polite term used by trained mages in writing and mixed company. Neutral in register, carries implicit social distancing. Use in GM Bible and rules content as the neutral analytical term.

hedge wizard

In-world peer contempt, used by trained mages among themselves. Never neutral. Do not use in player-facing, orientation, or formal rules content. May appear in NPC dialogue or lore where the contempt is the point.

hedge mage

Variant of the above, slightly less common. Same register and restrictions as hedge wizard.

"Wizard" is an archaism in Oath-Bound. Trained mages do not apply it to themselves. Its survival in "hedge wizard" is part of the contempt — it assigns an identity that nobody currently claims.

Petit magic

Petit magic is the formal domain name for cantrip-level workings — minor effects of limited range and power. It is institutional vocabulary, used in academic writing and formal classification.

At the table and in peer conversation, trained mages say cantrip. In player-facing content, cantrip is always correct.

Do not use "petit magic" in player-facing or UO content. It is GM Bible and rules register only.

Rustic adepts operate almost entirely within the domain of petit magic. This is the modal case, not a hard rule — exceptions exist and are noted in the Rustic Adepts rules page.

Foundation relationship terminology — patronus, patroni, cliens

Term Usage

patronus

The supervising priest in a formal Foundation pastoral relationship. Holds accountability for their clientes — not merely mentor but guarantor. Plural: patroni.

cliens

The subordinate priest in the relationship. Formal Foundation usage. Plural: clientes.

charge

Conversational equivalent for cliens. Use in player-facing and informal content where the Latin register would feel out of place.

patronus [domain]

A specialist patronus for a scoped relationship — e.g. patronus juridicus (oath law), patronus militaris (militant wing training). Domain qualifier distinguishes from the primary patronus. Always documented with scope and duration in Foundation records.

high patronus pastori

The dedicated pastoral authority for all of a Foundation’s paladins. Not a line patronus — the pastori qualifier signals advisory and counselling function, not administrative authority over field decisions. A Foundation-level appointment, not a personal one.

A patronus may have no cliens, one, or several. A cliens typically has one primary patronus. Additional specialist patroni are scoped to a defined purpose and duration. An undocumented specialist patronus arrangement is an irregularity the inquisitors will note.

Design Inspiration Comments

Every authored document may carry a design inspiration comment immediately after the file placement directive. This comment is not rendered in the published output but is visible in the source to anyone working on the document.

Format:

// DESIGN INSPIRATION: Brief note capturing the instinct, analogy,
// or reference that shaped the document's character. One to three
// sentences. Name the reference directly if it is useful.
// DESIGN INSPIRATION: The Portuguese pilot-major on a mission to
// Cathay. James T. Kirk. The authority is real, the chain is
// months away, the call is yours to make.
// DESIGN INSPIRATION: Vetinari for the happy face. Niska for the
// surgical decisiveness when necessary. The Scientology/Illuminati
// structure — the entry level is genuine, the deeper covenant is
// not disclosed to most participants.

The comment serves three purposes: it reminds the author what they were reaching for when they return to a document later; it gives Claude an immediate register and intent signal at the start of any editing session; and it briefs any future contributors on the design instinct without requiring them to reconstruct it from the content.

Not applied retroactively. Added to new documents and to documents undergoing active revision when the instinct is known.

Visage preposition

Use to as the associative preposition for visage relationships: "a fane to Thalenor Custos", "a House to Aurelion", "a service to Vestara". Works for buildings, rites, institutions, practitioners, and oaths. Replaces "of the [visage] visage" constructions.

Divine names

Use the confirmed public names and formal registers from the Gods and Divine Order baseline. Do not introduce new divine names or aliases without a formal decision recorded in theology/ corpus documents.

Primary public names: Aurelion (Oath), Vestara (Hearth), Caedran (Rule), Morvian (Death), Aelion (Craft), Minator (Measure), Veloran (Passage), Eridra (Harvest), Garrion (War), Thalenor (Justice).

Metadata completeness

Every AsciiDoc document must carry these header attributes:

  • :content-origin: — ChatGPT | Human | Claude | Mixed

  • :content-polish: — Raw | Polished | Approved

  • :content-type: — Commentary | Rules | Preface | Lore | Meta

  • :document-id: — unique identifier following the established format

Supersession

Any document that supersedes another must carry :supersedes: in its metadata listing the superseded filename. The superseded document must carry :superseded-by: with the superseding filename. Both updates are required. A supersession that updates only one side is incomplete.

The Open Call

When describing unmediated oath-binding mechanisms — spectacle, sacrifice, witness mass, arcane disturbance, or any other attention- getting declaration — use the term Open Call. It describes the category without implying a specific mechanism.

An Open Call is an attention mechanism, not a binding mechanism. It does not guarantee acceptance of the offered oath. Something capable of accepting it may notice. Whether it accepts, and on what terms, is outside the caller’s control.

The Founding Oath Controversy — Schools and Derived Terms

Four academically legitimate schools of interpretation exist. All are proper nouns. All have confirmed derived terms. A fifth position is institutionally dismissed and has its own terminology.

The Concordist School — a Concordist, Concordist theology

The Revisionist School — a Revisionist, Revisionist doctrine

The Limitationist School — a Limitationist, Limitationist position

The Imprecisionist School — an Imprecisionist, Imprecisionist scholarship

The fifth position — Disputational theology, a Disputer, the Disputational viewpoint. Deniers is an alternate dismissive. This position is not granted School status by the institutional church. The characteristic register when it must be acknowledged: "Disputational theology — if you can call it that."

Do not use "Heretical School", "Misrecognition School", or lowercase forms of any school name in any new output. When source documents use these non-conforming forms, apply the correct terms in derived output and note them for the next cleanup pass.

Language register for wyrd

The term wyrd and its mechanistic derivatives (wyrd-bending, wyrd distortion) are GM Bible and design-side register. In player-facing and UO content, the same phenomena are described through the language of divine access, divine favor, or what the gods notice. Both registers describe the same phenomena. Use the appropriate register for the target site.

As Above, So Below

The correct form is As Above, So Below. The variant "As Above, As Below" is non-conforming. Replace on any active editing pass.

Editorial Tooling — Vale Prose Linter

Vale (vale.sh) is the prose linting tool for the Oath-Bound corpus. It is installed via Scoop on Windows (scoop install vale), Homebrew on macOS (brew install vale), or package manager on Linux.

Vale requires Asciidoctor for native AsciiDoc parsing:

gem install asciidoctor

Baseline Configuration

The working .vale.ini for the Oath-Bound corpus root:

StylesPath = styles
MinAlertLevel = suggestion
Vocab = Oath-Bound

Packages = proselint, write-good

[*.adoc]
BasedOnStyles = Vale, proselint, write-good
write-good.E-Prime = NO

The Vocab = Oath-Bound line requires styles/config/vocabularies/Oath-Bound/accept.txt to exist. This file contains Oath-Bound proper nouns that would otherwise trigger spelling errors. Add new proper nouns to it as they surface.

write-good.E-Prime = NO disables the E-Prime rule (avoid all forms of "to be"), which is too aggressive for this corpus.

Active Style Packages

proselint — catches redundant phrases, weasel words, hedging constructions, and a range of imprecision markers. High relevance to AI tic patterns.

write-good — catches passive voice, weasel words, adverbs weakening assertions, and wordy constructions. E-Prime rule disabled (see above).

Running Vale

Single document:

vale path\to\document.adoc

Folder:

vale path\to\folder\

Interpreting Findings

Passive voice warnings from write-good.Passive require human review — some constructions are intentional in this register. Review each one in context before rewriting.

write-good.Weasel catches "various", "several", "many", and similar hedging words — high relevance to the Oath-Bound voice standard.

write-good.TooWordy catches constructions like "It was" — review in context.

Spelling errors (Vale.Spelling) after the accept list is populated are genuine finds — unknown proper nouns or typos.

Planned Enhancements

A reject.txt alongside accept.txt will flag retired terminology and slop list words as errors. This requires the voice reference three-document split to be completed first so the vocabulary table can be converted to Vale substitution rules. See -to-do.adoc.