Earned epithet & audience ledger

Begin with the deed that people disagree about

An epithet can look like a compact character description while actually carrying somebody else's judgment. Quay Saver and Bridge Breaker might refer to the same person and the same action. The useful writing question is not which phrase sounds more dramatic. It is who uses each phrase, which account of the event supports it, and what changes when the person refuses the description.

This workbench traces author-supplied reputation names through deed versions, audience knowledge and adoption intervals. It does not combine heroic adjectives or assign a moral score. You supply the proposed wording and the event that makes it consequential. The output shows whether that particular audience's recorded use has the prerequisites you declared at a selected chapter.

Use it for a contested reputation, an achievement that attracts unwanted credit, a propaganda label or a nickname whose significance changes after a revelation. Use the office-style tool for institutional appointments and recognized titles. Use the identity tool when the main problem is a concealed person behind an alias. A reputation label can coexist with either, but neither an office nor an alias automatically supplies its deed.

Four records that should not collapse into one

A deed record describes an authored event. A knowledge record says that an audience has encountered a specified version through a witness, report or rumor channel. An adoption record says that this audience praises, uses the label with hostility or rejects it during an interval. A personal-stance record says whether the named person accepts or rejects the epithet. These are different decisions.

The software does not convert knowledge into approval. A neighborhood may know about an action and never use the proposed name. It also does not convert an adoption entry into knowledge: if you enter a public use but supply none of the required knowledge records, the result identifies that unsupported dependency. This may reveal a missing transmission scene or a deliberately unexplained propaganda practice; it is not repaired by inventing a messenger.

Personal rejection does not erase other people's speech. A character may reject an accusation that opponents continue to repeat. She may also reject praise because it excludes collaborators. Preserve both the public use and her stance. Erasing the hostile name when she objects would make her preference incorrectly control every speaker in the story.

Write a dependency, not an adjective certificate

Each proposed epithet has a stable ID, a subject, literal display text and one to twelve required deed/version pairs. Every required deed must belong to that subject. The tool rejects an attempt to attach another person's event as if it satisfied the protagonist's prerequisite. It also rejects repeated deed requirements rather than counting the same event twice.

A requirement is your editorial contract. It does not prove that the wording follows logically from the event or that an audience's moral interpretation is justified. You can author a biased label and record a hostile adoption. The ledger then checks the stated dependencies while leaving the bias visible. Grounded means supported under the supplied model, not deserved, fair or historically authentic.

Choose requirements that would actually change your decision if rewritten. If an epithet supposedly depends on rescuing a harbor but remains unchanged when that rescue is removed, either the dependency is incomplete or the label has become an independent tradition. Describe that later tradition explicitly instead of treating the original deed as a decorative source note.

Read the two neighborhoods in the default example

The initial fictional fixture has Mira Vale opening a floodgate in chapter two. The lower quay drains, while an old footbridge is lost. One proposed name is Quay Saver; the other is Bridge Breaker. Both currently require version one of the gate event. The quay audience has a witness record. The bridge audience has a report record from chapter three.

At chapter four, the quay has a praising adoption for Quay Saver. The bridge has a hostile adoption for Bridge Breaker. The other two audience/label combinations have no adoption records. They remain unadopted, even though each audience has encountered the deed. Mira rejects both labels for different stated reasons. Neither rejection removes the two recorded public uses.

Remove the quay knowledge row and rerun. Its praise becomes unsupported by the required audience-knowledge record. Remove its adoption row instead and the label becomes unadopted. These changes answer different questions: the first asks how the audience could support its use; the second says no use has been recorded. Do not combine them into a single popularity score.

Original fictional scene: the two repair-fund notices

Mira arrived at the municipal print room with a basket of replacement hinges. The quay committee had asked her to repair the cupboard where it kept its donation forms. She expected a list of measurements, not a portrait.

On the first proof, her face occupied the space above QUAY SAVER. On the second, a rough drawing of the broken footbridge appeared above BRIDGE BREAKER. Both committees wanted the same printer and the same afternoon collection slot. Neither had asked Mira to choose the title.

The quay organizer explained that a recognizable name would help the fund. People remembered the water leaving their homes after Mira opened the gate. The bridge organizer replied that people also remembered walking an extra hour to reach the market. Their notices were not descriptions of two different people. They selected different consequences of one action.

Mira refused to sign either proof. She had turned the wheel, but three other workers had released the jammed mechanism. The first notice turned a shared decision into an individual triumph. The second turned the missing crossing into her entire identity. She set the hinges on the printer's table and asked both committees to list what they were actually collecting money to repair.

They did not immediately abandon the names. The quay organizer retained Quay Saver in the headline because supporters already recognized it. The bridge committee retained Bridge Breaker in a complaint attached to its repair estimate. Mira's refusal changed neither audience's existing vocabulary. It did change the signature line: she signed her personal name beside a request to credit the other workers.

In chapter seven, a new account of the gate operation circulated. It described the joint work that the earlier version had compressed into one person's action. The printer pinned the old notices beside the revised account. A writer now had a useful choice: let a committee reconsider its label, let it defend its selective wording, or show it continuing without acknowledging the revision.

This is an original fictional scene, not a historical case study or a claim about real communities. The repair fund keeps the consequences concrete. Each epithet directs attention toward a different claim on resources, and Mira's signature establishes an identity that neither headline fully owns.

What a personal name would change here

If both notices simply said Mira Vale, the competing repair arguments could still exist. The names would no longer compress those arguments into a recurring judgment. A later use of Bridge Breaker would not automatically remind the reader of the committee's selective account because that reference would not have been established.

If the narrator called her Quay Saver without attribution, the story could accidentally endorse one committee's framing. A writer may choose that narrative stance, but the ledger does not choose it. There is no narrator-approval field that turns audience adoption into objective description. Attribute the epithet where the viewpoint matters, and decide separately how the narration treats it.

Apply this method by writing the ordinary personal name into the same scene, then restoring the epithet. Identify the information and judgment restored by the change. If nothing changes except ornamental grandeur, the proposed reputation name may not need this much machinery. A short descriptive nickname can remain a simple authored choice when no consequential dependency exists.

Reopen a reputation without deleting the old account

The default ledger includes a second version of the gate event, effective from chapter seven. Its description records joint action rather than sole credit. Query chapter eight and version-one prerequisites reopen as disputed. The earlier chapter-four query still uses the first effective version. The comparison field can display what changed between those scene points.

This is a versioned account model, not a universal theory of truth or a complete manuscript history system. The effective chapter says when that version enters the supplied scene ledger. It is not a file modification date. If your actual rewrite changes what was true in every earlier chapter, update the editorial model deliberately and retain a separate manuscript version; do not pretend that a later in-story account automatically represents that kind of rewrite.

A revised prerequisite does not prove that the phrase is false. Joint work might still support Quay Saver in an audience's vocabulary. The dispute means the old version-specific contract needs review. If you retain the epithet, update its prerequisite consciously. A change of wording in the deed description alone does not silently approve all dependent reputation names.

Knowledge does not travel with the author's cursor

After changing an epithet to require version two, the audience still needs a knowledge record for that version. A witness entry for the old account is not a subscription to every future revision. Add the actual transmission point, with its channel, only when the story supports it. Before that chapter the required knowledge remains absent.

Witness, report and rumor are supplied channel labels. None produces a confidence percentage, a historical proof or an automatic ranking of credibility. A rumor record can explain why a hostile name spreads without certifying the rumor outside the authored model. If reliability is important to the scene, establish it in the prose and keep the relevant explanation with the source manuscript.

Do not put an audience's private revelation into an earlier knowledge row simply to make a warning disappear. That would erase the creative problem the tool exposed. Add a transmission scene, delay the adoption, distinguish a smaller audience or retain the unsupported state as a documented writing question.

Intervals make reversals inspectable

Audience adoption uses inclusive from/to chapters. A null end leaves the interval open. One audience cannot have overlapping adoption entries for the same epithet: the workbench needs a single declared stance at a selected point. End one entry before starting the next. Personal-stance intervals follow the same non-overlap rule for each epithet.

If a crowd is genuinely divided at one time, define meaningful audience groups instead of entering contradictory records for one undifferentiated public. The current model does not calculate proportions or social-network diffusion. Splitting an audience should reflect a story distinction, not manufacture a majority by duplicating rows.

Use the comparison chapter to inspect state and dependency changes, including a newly learned account or personal rejection. It compares queries against the records you currently supplied. It does not store an immutable earlier publication, automatically recover overwritten descriptions or prove that a past export matches today's ledger.

Keep the author audit private and the scene precise

The dedicated handoff is explicitly a private author audit. It includes prerequisite traces and current authored descriptions that an audience may not know. A visible-results export and a private project can also reveal those details. This tool does not promise a spoiler-safe public reputation sheet; prepare public notices separately from the author's dependency records.

The local bounds are thirty people, one hundred and twenty deed revisions, sixty labels, two hundred and forty knowledge records, two hundred and forty adoptions and one hundred and twenty personal stances. Select up to four audiences and at most one hundred and twenty label/audience combinations. Split larger projects into meaningful story scopes rather than expecting an unbounded world simulation.

Before adopting a result, read one actual line in which the epithet is spoken. Identify the speaker's audience, the relevant chapter, the account available to them and what the named person does in response. A working ledger earns its place by clarifying that scene, not by making every reputation look consistent or giving every character an elaborate title.

Does grounded mean the character deserves the name?

No. It means the declared deed versions and audience-knowledge prerequisites are present. Moral judgment, accuracy of the wording and narrator endorsement remain separate writing decisions.

Why is a label still used after the person rejects it?

Personal acceptance does not control other speakers. The ledger retains the audience adoption and the person’s refusal so you can write their conflict. Ending public use requires an explicit adoption interval change.

Can a rumor establish a historical fact?

The rumor channel records how an authored audience encounters an account. It does not certify external truth or infer a reliability percentage. Explain disputed evidence in the scene rather than treating a channel label as proof.

Is the export safe to show to readers?

The dedicated audit is private and can include deed descriptions unknown to audiences. Visible results and projects can also expose setting details. Prepare a separate public document; no spoiler-safe export is promised here.