Fictional reign numeral ledger

One person, more than one numbered history

A reign numeral can look like the smallest part of a character's name until it appears on two incompatible props. The person is the same, the reign name is the same, yet a letter says II and a seal says IV. Before inventing a second sovereign or correcting a number, ask which history each object counts. This workbench makes that counting contract explicit.

It is for invented chronicles, fantasy courts, comics and games that reuse reign names. Supply people, separate numbering series, earlier histories and dated accessions. The tool follows those declarations, retains disputed alternatives and checks an entered number against them. It does not determine who was a legitimate ruler, supply a real dynasty's customs or certify a historical inscription.

This is different from choosing an impressive title. An office-style tool can resolve which office or courtesy form belongs in a scene. Here the main question is ordinal: which earlier entries contribute to this number, and does a returning person count again? A title can remain unchanged while the answer changes. A beautifully chosen name cannot compensate for an unstated counting rule.

Original fictional scene: the courier with two seals

Sela's courier arrives at the inland gate with a southern road permit. The wax carries Vela IV. The envelope inside is addressed to Vela II of the North Crown. The gate officer compares the two marks and asks whose permit the courier has borrowed. The courier answers that both belong to Sela, who bears the reign name Vela under two crowns.

The officer knows the northern household, where one earlier Vela is counted before Sela. The southern road office counts three earlier accessions in its own sequence. The two objects refer to one person through different institutional histories. Changing IV to II on the southern seal would make the permit less consistent with that office's declaration, not more truthful about Sela.

An archivist brings another northern list. It includes Meral's disputed tenure between the earlier holder and Sela. On that list Sela is Vela III. The officer cannot solve the disagreement by announcing that one spelling must describe another person. The question is whether this particular chronicle includes Meral. The chancery issuing the envelope excludes that entry; the archivist preserves the rival claim beside it.

Later, Sela returns after an interruption in the reign. A new clerk proposes increasing the northern numeral merely because another accession ceremony occurred. The chancery's declared rule counts people, so Sela retains the already assigned northern number. An accession-counting rule would produce another result. The restoration has to be written with the institution's rule in view, not as an automatic renaming of the individual.

This is an original fictional scene. Its chancery follows one declared choice, while the initial workbench leaves the disputed holder unresolved so you can inspect both alternatives. No real court or historical number is being described. The story shows how a name can carry jurisdiction, continuity and a contested account without erasing the personal identity underneath.

Vela works here because the story deliberately reuses a reign form to signal institutional continuity. That is a creative explanation, not an etymology. If Sela chose a new name and opened a new equivalence key with no predecessors, the counter could start at I. That would change what the court claims to continue. Merely changing the visible spelling while retaining the old key would not create that break in this model.

Define the series before entering the suffix

Here a reign display is the authored public name used by a holder, and a series is a declared scope sharing one counting policy. Keep the person's stable ID and personal name separate from that display. The same person can appear in several series, and two different people can use the same reign name. Do not use the visible word as the identity key. In the example, sovereign identifies Sela while north and south identify separate numbering series.

Each series declares people or accessions as its unit. Under people, a person retains an ordinal within the same series and name key on a later included return. Under accessions, each included event advances the count. Neither is presented as a universal royal custom. They are two supported rules for your invented world, and the tool does not choose between them for you.

The name key is also explicit. Entries with key vela share a counter within one series even if their authored displays are Vela and Véla. This does not establish that those spellings are linguistically equivalent. It records the author's grouping. Another key opens another declared history and therefore needs its own earlier-history record.

Do not turn every typographic variation into a fresh lineage just to make a number work. First decide what the chronicler treats as the same reign name. Then choose the display appropriate to the prop or scene. If the connection itself matters to readers, explain it in the fiction; a private data key is not reader-facing evidence.

Earlier history must be known, zero or explicitly unknown

Every used series and name key requires a baseline. priorCount states the earlier count or is null. Zero is a deliberate claim that no earlier counted member belongs in this scope. Null means the earlier count is unknown. The tool never converts a missing past into the convenient first numeral.

People counting also needs priorPeople, a complete ordered list containing exactly priorCount known person IDs. Its position assigns the earlier ordinal. This lets an already listed person return without consuming a new number. A list with duplicates, unknown people or the wrong length is rejected. The software checks the structure of the author's claim of completeness; it has not independently verified the chronicle.

Accessions counting can use a known count without a list of earlier people. If you later switch that series to people while leaving priorPeople unknown, the resulting person-based numerals are unknown. The dedicated policy control changes only the counting unit. It preserves earlier history rather than fabricating a list to keep the output looking finished.

The example's northern baseline has one known earlier person. Its southern baseline has three earlier accessions and no ordered person list. Those are different pieces of information. Keeping them distinct is useful when a production team has a reliable count on one prop but incomplete identity records behind it.

Follow the worked ledger in chronological order

The disputed northern entry occurs at point 2. Sela's first northern and southern entries occur at point 4. Sela returns in the north at point 7. A later northern entry is explicitly outside the count. These are authored integer time points, not interpreted calendar dates. Entries are sorted by time and explicit tie order, not by the order in which you pasted JSON.

With Meral excluded, the northern baseline of one makes Sela the second counted person. Including Meral makes Sela third. The southern counter starts from three, so Sela's first southern accession is fourth in both alternatives. The returned northern entry reuses Sela's assigned ordinal under people counting. The different display Véla does not reset key vela.

Now use Compare one series' counting rule and change north to accessions. The first northern entry remains II or III, but the return becomes III or IV. The existing claim II on that return is contradicted by all the newly declared included histories. That is a rule-based change, not another random name draw. Undo restores the matching unit change while preserving other inputs.

If two entries share the same series, key and time, give them distinct order values. Switching their declared order can change who receives the earlier number. An ambiguous tie is rejected instead of being settled by incidental row order. Simultaneous entries in independent scopes do not share a counter merely because the dates match.

Disputed inclusion creates alternatives, not a verdict

Each entry references an include, exclude or unresolved decision. Several entries can share one decision ID. In every hypothetical history they then share the same inclusion choice, including across crowns. This preserves a declared connection instead of independently toggling linked events and inventing combinations the author never supplied.

The tool exactly enumerates up to ten used unresolved decisions, producing at most 1,024 alternatives. Unused decisions do not change the histories. Beyond that bound it stops and asks you to resolve or split the ledger; it does not return one convenient branch as a completed answer. The supported choices are independent between different decision IDs. More complicated relationships need an explicit redesign of the authored scope.

The main table shows every resulting numeral possibility. The history selector lets you inspect one hypothesis and its predecessor traces. Its caption and copied trace remain hypothetical. Inspecting it does not edit decisions, change the overall claim check or make the full export forget other alternatives. Resolve an input decision and recalculate if you actually intend to change the model.

Check what a letter or inscription asserts

The optional claimed field contains the number a prop currently prints. matched means that number agrees with the declared included histories. conditional means it agrees only under some alternatives or applies only when the entry is included. contradicted means no included computed number matches it. unverifiable means the earlier history cannot support a number. excluded means the entry receives none under the declared decisions. No supplied claim is treated as evidence that its own number must be correct.

These states are writing decisions, not rulings about legitimacy. A character can deliberately use a partisan chronicle. A quoted old letter can retain a number that a later narrator disputes. The useful question is which convention the object claims to follow and whether the reader has enough information to understand that claim. This workbench does not prove a mystery clue is fairly disclosed; that requires a separate reader-knowledge review.

Copy all numbering possibilities preserves inclusion and uncertainty. Copy this hypothetical trace states which branch was inspected. The private handoff contains every bounded history, entry order, before-count and reused-number reference. It can expose story disputes and personal identities, so review it before sharing. Saving a favorite retains the entry and crown context; the same displayed name in two crowns stays separate.

Keep presentation separate from the counting contract

The optional Roman display is an internal rendering convention over computed integers from 1 to 3,999. It consumes values using M, CM, D, CD, C, XC, L, XL, X, IX, V, IV and I in descending order, with values 1000, 900, 500, 400, 100, 90, 50, 40, 10, 9, 5, 4 and 1 respectively. Decimal display uses the same computed numbers. Changing this presentation cannot repair a contradicted claim or supply missing history, and it is not a claim about any real court's typography.

Before approving a numbered form, inspect the person ID, series, exact name key, baseline, inclusion choices and reaccession rule. Then decide which form belongs in the scene. If all you need is an unnumbered personal-name candidate, use a naming workbench. If the question is who currently holds an office, use the ceremonial-style tool. Here the outcome is a defensible fictional counting trail behind a name, with the unresolved parts still visible.

Does an entered numeral establish the correct chronology?

No. claimed is a statement to check against the declared history. It cannot supply a missing baseline or decide a disputed inclusion. The tool reports matched, conditional, contradicted, unverifiable, excluded or not supplied within this model.

Why does the same person receive different numbers in two crowns?

The counters belong to the series and exact name key. Two crowns can declare different earlier histories or counting units. Their numbered forms can refer to one stable person without merging the counters or inventing a second individual.

Can I switch spelling and automatically reset the number?

A display change alone leaves the explicit key unchanged. To establish a different counted reign name, supply another key and its own baseline. The software does not infer linguistic equivalence or historical naming customs.

Does selecting a hypothetical history resolve the dispute?

No. It only previews one supplied alternative. The overall claim check, all-possibilities copy and private handoff retain the alternatives. Change an input inclusion decision explicitly if you intend to change the model.