Conflict Register (human-readable view)

⬇ Download this section

Companion to: Layered Enforcement (§11) · Schema (_data/rules/schema.yaml) · Precedence Algorithm (_data/rules/precedence.yaml) · Canonical Register (_data/rules/conflict-register.yaml). This page is the hand-maintained human-readable twin of the canonical YAML. Rules read top-to-bottom, grouped by domain. For full schema details and machine-readable definitions, use the YAML.


How to read this page

Each rule lists:

Resolution always walks layers [platform, format, persona, general] from highest precedence to lowest; the first matching override wins. Some rules have precedence: [general] to indicate the rule is never overridable (system-wide compliance).


Headline rules

headline.char_count—H1 character count range

headline.intent_advisory · headline.name_expert_advisory · headline.etk_advisory—TH B2C headline advisories (flag-only)

headline.seo_title_char_count—SEO title char count

headline.promo_title_char_count—Promo / homepage title

headline.meta_description_char_count

headline.formula—required headline formula / template

headline.questions—question-format heds permitted?

headline.number_lead—number-led heds positive / neutral / avoid?

headline.what_to_know_endings—”What to Know” endings permitted?

headline.did_you_miss—”Did you miss” patterns

headline.numerals_in_heds

headline.quote_style—single vs double in heds

headline.periods—periods at end of heds permitted?

headline.ampersands—ampersands in heds

headline.casing—title case / sentence case

headline.h2_keywords—H2 keyword requirements

headline.intro_word_count

headline.front_load_keywords


Body rules

body.word_count—total article body word count

body.faq_block_word_count—per-question/answer block

body.paragraph_max_sentences—max sentences per paragraph

body.celebrity_names—bold + tag-page linking

body.italics_targets / body.italics_excluded / body.podcasts_format


Punctuation rules—load-bearing cross-publication divergences

punctuation.banned_marks—marks flagged for manual removal

punctuation.em_dash_surrounding_spaces

punctuation.oxford_comma

punctuation.ellipsis_surrounding_spaces


Grammar rules

grammar.couple_verb_agreement—singular vs plural for couples / pairs / duos (excluding mashups)

grammar.contractions_avoided


Structure rules

structure.sister_rule_heds—onpage / promo / SEO must be sister-style with shared keywords

structure.faq_answer_first—first sentence after each H2 must directly answer

structure.required_article_structure—format-prescribed structure

structure.status_bar—Status Bar element directly under headline

structure.forecaster_pull_quote—named-forecaster pull quote

structure.three_signals_to_watch—Three Signals to Watch boxed callout


Voice / tone rules

voice.tone_north_star—specific tone reference / archetype

voice.audience_framing—demographic vs psychographic

voice.banned_words_aging—words banned for negative aging framing

voice.banned_phrasing_demographic—demographic-stereotyping phrasings

voice.banned_slang—trendy / juvenile slang

voice.politics—partisan / political framing

voice.preferred_substitutions_beauty—preferred WW beauty vocabulary


Compliance rules—system-wide; mostly NOT overridable

compliance.byline—named individual byline required

compliance.ai_disclosure

compliance.no_unverified_facts

compliance.human_review_required

compliance.helpful_content

compliance.no_keytakeaways_at_top

quality.health_claim_sources—required source authority for health claims

quality.product_recommendations


Linking rules

linking.anchor_text


Media rules

media.hero_image

media.platform_thumbnail

media.gifs

media.subtitle_field


CMS rules

cms.required_fields


Faith rules

faith.god_word_permitted


Discoverability / platform rules

platform.content_categories—platform-specific topic categories

platform.publishing_cadence


Format-specific patterns (additive only—format introduces, no general equivalent)

format.faq.pattern_h1

format.recipe.dek_format

format.timeline.chronological_order


Publication-specific rules

publication.us-weekly.brand_italicization

publication.us-weekly.tv_film_title_italics


Cross-cutting—explicit-language policy

explicit.headlines_substitutions—approved substitutes for “NSFW” / suggestive language

explicit.galleries_stricter


Worked-Example Roll-Up

For a piece described as { persona: curious-optimizer, format: faq, platform: apple-news }, here’s the resolved value for every applicable rule:

Rule Resolved Why
headline.char_count 90–120, target 110–119 Platform (apple-news) wins over Format (FAQ has no char count override) and General
headline.formula [Topic] [Question Word]: [Specific Question Answered] Format wins (no platform override on formula)
headline.questions avoid Platform (apple-news data-validated)
headline.h2_keywords every H2 must include Google Trends / PAA keyword Format (FAQ)—additive over General’s “primary in ≥1 H2”
body.word_count none No applicable layer
body.faq_block_word_count 100–200 words Format (FAQ)—additive
body.paragraph_max_sentences 3 Format (FAQ)
voice.audience_framing psychographic-only Persona (curious-optimizer)
media.subtitle_field required Platform (apple-news)
media.platform_thumbnail 300×300px min, 1:2 to 3:1 Platform (apple-news)
compliance.ai_disclosure standard + Apple News restriction (byline/co-byline + News Publisher metadata + AI-use explanation) General + Platform restriction stacks
punctuation.em_dash_surrounding_spaces true General (AP default—spaces; Apple News doesn’t override)
punctuation.oxford_comma false General (no override)
grammar.couple_verb_agreement singular General (Apple News doesn’t override; no publication selected)

Notice that Persona, Format, and Platform all contributed independently—no contradictions—and the resolution is deterministic per the precedence algorithm.


Maintenance

When this register changes:

  1. Update _data/rules/conflict-register.yaml (canonical, machine-readable)
  2. Update this page (docs/conflict-register.md)—hand-maintained twin
  3. Update the source doc page (e.g., docs/<format>.md)
  4. Bump csa-content-standards version in api/reference.json, master-reference.md
  5. Add changelog entry
  6. Run scripts/build-downloads.sh to regenerate downloadable copies in assets/sources/ and assets/sources/rules/

For schema changes, update _data/rules/schema.yaml and bump schema_version. For algorithm changes, update _data/rules/precedence.yaml and bump algorithm_version.