MORIS MEDIA / PROTOCOL 04

Input Placeholders & Variables

Mandatory publication and execution protocol. The source instructions below retain their original wording, with line references to the supplied master prompt. All relevant requirements are binding; overlaps with other pages are intentional.

Execution instruction

Read all source requirements on this page and apply them to the approved topic, geographic level, workbook, and content fields. Never substitute a summary for a binding requirement. Consult the master execution overrides for precedence and the final validation protocol before export.

Binding source requirements: lines 4–7

0004 | ONLY THREE INPUT PLACEHOLDERS
0005 | Here is the topics which has been approved:
0006 | 
0007 | Here is country state and city centric topics and sections breakdown:

Binding source requirements: lines 210–230

0210 | The final output must preserve the approved Excel column structure established in this master prompt.
0211 | The final workbook must contain content aligned with the geographic level specified for the assignment.
0212 | For a city-centric assignment, the final content must be city-centric.
0213 | For a state-centric assignment, the final content must be state-centric.
0214 | For a country-centric assignment, the final content must be country-centric.
0215 | The actual target location must always be read directly from the Excel City column, regardless of whether that value represents a city, state, or country for the current assignment.
0216 | The final generated content must use the actual target-location value from the Excel City column rather than leaving a city, state, country, or location placeholder.
0217 | The only variable permitted to remain inside final generated content is:
0218 | {year}
0219 | The {year} variable must always remain exactly as {year}.
0220 | Never replace {year} with the current year, a manually entered year, a calculated year, or any numeric year.
0221 | Do not change {year} to {Year}, {YEAR}, [year], [YEAR], “current year,” or any other variation.
0222 | The exact variable {year} may be used naturally throughout H1s, H2s, short SEO headings, hook headings, body content, FAQs, CTAs, banner content, descriptions, comparisons, ranking constructions, service explanations, and other relevant content fields.
0223 | Exception: {year} must not be used in the Meta Title.
0224 | The Meta Title must therefore be written without {year} even when {year} appears elsewhere throughout the article.
0225 | No other content variable may remain in the final Excel output.
0226 | Variables supplied as instructions or inputs, including {Topic}, may be used to determine what must be written but must be replaced by their actual supplied values in the final workbook.
0227 | Every location article must be independently researched, independently structured, independently written, independently localised, and independently validated.
0228 | Changing only the target location in previously written content is strictly prohibited.
0229 | The content must remain exclusively related to the supplied {Topic}, its directly relevant service category, and closely connected supporting services necessary to explain the topic properly.
0230 | Unrelated Moris Media services must not become the primary subject merely because Moris Media offers them.

Binding source requirements: lines 553–570

0553 | 10. LOCATION GOVERNANCE
0554 | Use only 1 geographic level according to the assignment.
0555 | City-centric article: use the actual city.
0556 | State-centric article: use the assigned state as the target location.
0557 | Country-centric article: use the assigned country as the target location.
0558 | Never unnecessarily stack:
0559 | City + State
0560 | City + Country
0561 | State + Country
0562 | City + State + Country
0563 | in the same heading.
0564 | The master template may use {city} as the target-location placeholder.
0565 | During final execution, the target location must be populated according to the article assignment.
0566 | The variable that must remain unchanged is:
0567 | {year}
0568 | Never replace {year} with a manually written calendar year.
0569 | {year} may appear in Banner content, H1, H2, Section Headings / Hook Lines, body content, FAQs and CTAs where relevant.
0570 | {year} must NOT appear in the Meta Title.

Expanded global production requirements

Universal geographic scope and application

This protocol applies to approved service articles for any country, state, province, territory, region, city, or comparable administrative area. Examples involving India are illustrative only. No Indian city, law, currency, language, ranking claim, media market, or business environment may be presumed to apply to other countries. Research each location independently and use its actual administrative terminology.

Input geographic tokens are {country}, {State}, {city}, and {year}. When geographic context needs 2 levels, use {State}, {country} or {city}, {country} or {city}, {State}, according to the page's approved scope. Never put {city} and {State} on the same line unless the approved assignment explicitly requires that pair; when it does, do not add {country} to that line. Never stack all 3 geographic levels in a heading. In location-first headings prefer only the primary geographic level. Country-level pages use {country} alone. State-level pages may use {State} with {country} for essential clarification. City-level pages may use {city} with either {State} or {country}, but not both.

In metadata fields Meta Title, Meta Description, and Meta Keywords, no curly-brace variable is permitted, including {country}, {State}, {city}, {Location}, {Agency_type}, or {year}. Populate those fields with researched literal location names and approved facts before export. The other article fields may contain permitted template variables only when the assignment explicitly requests template output; for publication-ready geographic rows, replace geographic placeholders with actual target values. Preserve {year} literally wherever approved outside metadata.

Digits, numeric claims and measurement

Write numeric quantities as digits, not spelled-out number words, in publication output: use 10 sections, 62 columns, 850 words, 5 examples, 12 years, and 4.5 rating. Retain natural fixed names and quoted official titles when spelling is part of a verified proper noun. Numeric evidence must be traceable, scoped to the correct geography and date, and supported by a credible source. Never turn an estimate into a verified result. Keep units, currencies, dates and percentages clear.

Variable precedence and resolution

The 3 geographic variables are case-sensitive: {country}, {State}, {city}. {Location} is an optional banner alias resolved from the geographic target; {Agency_type} is an optional business-classification token. {year} remains a literal token in approved non-metadata content. Do not create alternate spellings such as {state}, {City}, {Country} or {Year}. The input record must identify which geographic level controls the article. For final publication, resolve all geographic tokens into literal place names. For a reusable template, retain the approved tokens only outside metadata.