Glossary Update Workflow¶
Editorial workflow — instantiates Semantic Drift Monitoring
The editorial pipeline that turns an approved drift verdict into a revised, example-anchored definition published to readers.
A Glossary Update Workflow is the forward-moving pipeline that takes a decision about drift and turns it into a published definition people can read and use. Where a diagnosis says "this term has widened," the workflow does the work of deciding what to do about it — preserve, revise, split into senses, add a qualifier, or deprecate — and then ships the result: writes the new definition, pins it with examples and non-examples, and pushes it to the surfaces where readers meet the term. Its defining orientation is prospective and reader-facing. It is not the record of what changed and it is not the version-and-compatibility scheme; it is the editorial act of producing the new canonical text and getting it in front of people cleanly.
Example¶
A software company's developer-documentation team maintains the public glossary for its API. Monitoring and an audit have established that the term "deprecated" has drifted: engineers now use it for two different situations — endpoints that still work but are discouraged, and endpoints scheduled for removal — and external developers keep guessing wrong. The workflow takes it from there. Applying its update rule, the team decides not to preserve the fuzzy single sense but to split it: "deprecated" (discouraged, still supported) versus "sunset" (removal date set). It drafts both definitions, anchors each with a worked example and a pointed non-example ("a sunset endpoint is not merely discouraged — it will stop responding on the posted date"), and runs the change through review. Then the communication step publishes: the revised entries go live with an effective date, a short changelog note at the top, and a banner on the two endpoints most affected. A developer opening the glossary next week sees the new senses, the examples, and when the change took effect — not a silently swapped paragraph.
How it works¶
- Decide the disposition. Convert the drift verdict into one editorial action — preserve, revise, split, qualify, or deprecate — chosen deliberately rather than defaulting to "rewrite."
- Draft to the disposition. Write the new definition text, and pin its boundary with a matched example and non-example[1], so the revised sense is fixed by demonstration and not by wording alone.
- Review before publish. Route the draft through whoever must sign off, so a definition change isn't a unilateral edit.
- Publish with a change frame. Push the new text to reader surfaces together with an effective date and a short note of what changed — the update arrives visibly, not as a silent replacement.
Tuning parameters¶
- Disposition bias — how readily the workflow revises versus preserves; an eager bias keeps definitions current but risks churn, a conservative one protects stability but lets text lag live use.
- Example density — how many examples and non-examples anchor each entry; more pins the boundary tightly but bloats the glossary and slows authoring.
- Review depth — how many sign-offs a change requires; heavier review guards against bad edits but slows publication, lighter review is fast but riskier.
- Publication reach — how loudly the change is surfaced (a quiet entry edit versus banners and notices); louder reach prevents readers missing the change but spends attention and can over-signal a minor tweak.
When it helps, and when it misleads¶
Its strength is that it closes the loop: monitoring and audits only produce awareness, but the workflow produces the artifact readers actually consult, with the change made visible rather than slipped in. Its failure mode is definitional churn — an over-eager workflow that rewrites the glossary for every trend produces a definition of record that is never stable long enough to coordinate on, the very outcome the archetype warns against. A related misuse is publishing revised wording with no examples, so the new boundary is asserted but not demonstrated and readers re-drift immediately. The guarding discipline is to require an approved verdict as the trigger (not a hunch), to anchor every revision with examples and non-examples, and to let stable terms stay stable.
How it implements the components¶
definition_update_rule— it owns the editorial decision that turns a verdict into an action: preserve, revise, split, qualify, or deprecate the definition.change_communication_plan— it publishes the revised text to reader surfaces with an effective date, a plain note of what changed, and examples that distinguish the new sense.
It does not assign the legacy_compatibility_note that lets an old and a new definition run side by side — that coexistence scheme is Semantic Versioning Policy, the nearest twin: the workflow writes and ships the new definition, while versioning gives definitions dated, versioned identities and compatibility rules. It also does not keep the baseline_meaning_snapshot and drift_governance_owner provenance of what was changed and by whom — that is Definition Change Log.
Related¶
- Instantiates: Semantic Drift Monitoring — it is the mechanism that converts a drift decision into a published definition.
- Consumes: Terminology Audit — the audit's classified verdict is the trigger the workflow acts on.
- Sibling mechanisms: Terminology Audit · Corpus / Usage Monitoring · Definition Change Log · Semantic Versioning Policy · Policy Language Review · Stakeholder Interpretation Check · Usage Exception Registry
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Glossary Update Workflow operates as a repeatable ordered procedure or handoff sequence that coordinates action because it the editorial pipeline that turns an approved drift verdict into a revised, example-anchored definition published to readers.
Independent corroboration: The frozen evidence defines Glossary Update Workflow as 'The editorial pipeline that turns an approved drift verdict into a revised, example-anchored definition published to readers', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Controlled-vocabulary editorial governance supplies approval, revision, and publication workflow.
Related originating lineages:
- Linguistics & Semiotics — Ostensive definition and matched examples materially anchor revised semantic boundaries.
Review resolution: Both reviewers agree that library_information_science is primary: Controlled-vocabulary editorial governance supplies approval, revision, and publication workflow. I retain linguistics_semiotics only as formative lineage, not as a list of later applications. I resolve origin_mode as cross_disciplinary_synthesis because the artifact joins distinct disciplinary contributions. I resolve domain_reach as universal because it is broadly applicable across essentially all domains. Encyclopedia synthesis is true because the exact generalized packaging is an encyclopedia-authored combination or refinement.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Johnson, K., & Bulla, A. J. "Creating the Components for Teaching Concepts". Behavior Analysis in Practice 14, 785–792 (2021). Prescribes matched example/nonexample pairs that isolate a critical feature and sharpen the boundary of a concept. registry ↩