Style Guide Revision¶
Governance artifact — instantiates Marked Default Audit
Encodes an audit's decision as a durable rule in the style guide — what to mark and how, which asymmetries are justified and why, and how compliance is checked going forward.
Style Guide Revision is the mechanism that turns a one-time audit verdict into governance. Where its siblings find or fix a specific instance, this one writes the rule: it states the revision target as prospective policy, records which asymmetries are deliberately kept and why, defines how future compliance is checked, and communicates the new standard to the people who author labels. Its one idea is that it governs future naming, not any single existing label. It never relabels an instance itself — that is the job of the audits and reviews it draws from — it sets the standard those mechanisms and every future author will follow.
Example¶
A software company's documentation team has just learned, from an audit, that code examples default to macOS while Windows and Linux are relegated to "other platforms." Rather than patch each page, the docs lead revises the style guide. The revision target becomes a stated rule: every code example names its platform explicitly; no platform is the unnamed default. An exceptions section records that keyboard-shortcut docs may keep an OS-specific default because the physical keys genuinely differ, with the reasoning attached — a justified asymmetry record. A linter plus a pull-request checklist enforce the rule on new content — the validation and monitoring check. And a changelog entry plus a team announcement roll it out — the transition communication. The norm is now governed rather than re-argued page by page.
How it works¶
- Convert the audit decision into a stated rule — what gets marked, on which dimension, and how the default is named.
- Record the justified exceptions with their reasons, so necessary asymmetries survive the push for symmetry.
- Wire the compliance check — linters, checklists, or review gates that catch violations in new work.
- Communicate the change to authors and cite it in the guide so the rule is discoverable at the moment of writing.
Its distinctive quality is that it is meta: durable, prospective, and about the pattern rather than any single label.
Tuning parameters¶
- Rule strictness — a hard prohibition versus a recommended default. Stricter is enforceable but less flexible when a case genuinely needs an exception.
- Exception latitude — how easily a justified asymmetry can be recorded and kept. Too tight forces false symmetry; too loose lets the old norm survive under "exceptions."
- Enforcement automation — human review versus automated lint. Automation scales but throws false positives on legitimate content-naming.
- Rollout pace — immediate cutover versus a deprecation window for existing content.
When it helps, and when it misleads¶
Its strength is preventing recurrence: by governing the pattern, it stops the same asymmetry from being reintroduced by the next author, and its exceptions record is the archetype's honest answer to "justified marking." Its failure mode is prescriptivism[n1] — a fossilized rule can itself harden into a hidden norm, mandating a "symmetry" that later reads as awkward or that re-marks a group in a new way. The classic misuse is banning a list of words without encoding the underlying default logic — a checklist masquerading as governance. The guarding discipline is to encode the relation (name the default; mark parallel cases on the same dimension) rather than a term blacklist, keep the exceptions record live rather than write-once, and periodically re-audit the guide itself.
How it implements the components¶
revision_target— states, as durable policy, what changes and on which dimension marking is to be applied.justified_asymmetry_record— documents the asymmetries deliberately kept, with the reasoning that justifies them.validation_and_monitoring_check— defines the compliance checks (lint, checklist, review gate) that keep future work honest.transition_communication— announces the new standard and cites it where authors will encounter it.
It does not detect instances or perform the per-label label_or_category_revision — those belong to Naming Markedness Audit and Classification Markedness Audit; the style guide sets the rule they follow rather than rewriting any single label itself.
Related¶
- Instantiates: Marked Default Audit — preserves the audit decision as durable naming governance.
- Consumes: the audit decisions from Naming Markedness Audit and Classification Markedness Audit, which it encodes as prospective rules.
- Sibling mechanisms: Naming Markedness Audit · Default Label Review · Inclusive Language Markedness Review · Classification Markedness Audit · Symmetry Labeling Matrix · Search and Documentation Scan · Stakeholder Interpretation Review
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Style Guide Revision operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it encodes an audit's decision as a durable rule in the style guide — what to mark and how, which asymmetries are justified and why, and how compliance is checked going forward.
Independent corroboration: The frozen evidence defines Style Guide Revision as 'Encodes an audit's decision as a durable rule in the style guide — what to mark and how, which asymmetries are justified and why, and how compliance is checked going forward', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Analysis, Modeling & Optimization — Style Guide Revision includes features of an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution, but its defining operation is a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Communication & Media Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Encoding review decisions as durable editorial rules is style governance.
Related originating lineages:
- Art & Aesthetics — Visual art, composition, and design practice supplies a parallel or contributing lineage for the mechanism's defining operation: encodes an audit's decision as a durable rule in the style guide — what to mark and how, which asymmetries are justified and why, and how compliance is checked going forward.
- Law & Governance — Exceptions need recorded rationale.
- Organizational & Management Science — Compliance must be checked.
- Rhetoric — Rhetorical invention, audience adaptation, and persuasive communication supplies a parallel or contributing lineage for the mechanism's defining operation: encodes an audit's decision as a durable rule in the style guide — what to mark and how, which asymmetries are justified and why, and how compliance is checked going forward.
Review resolution: The blind reviewers agree that communication_media_studies is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Prescriptivism — the stance that usage should conform to codified rules. Useful for consistency, but risky when a fossilized rule outlives the rationale that produced it and itself becomes an unexamined norm — which is why a markedness style rule needs a live exceptions record and periodic re-audit rather than permanence. ↩