Yezur Wiki:Conventions - Revision history

Alompan: Conventions: place qualifiers take 'in' and the house word is country; add the single-point map indicator; record that files are categorised (report 51, 52, 54)

2026-08-04T20:08:32Z

Conventions: place qualifiers take 'in' and the house word is country; add the single-point map indicator; record that files are categorised (report 51, 52, 54)

← Older revision		Revision as of 20:08, 4 August 2026
Line 66:		Line 66:

	* '''Language articles''' use the "''X'' language" form (e.g. [[Gaillean language]]). Native names and other aliases become '''redirects'''.		* '''Language articles''' use the "''X'' language" form (e.g. [[Gaillean language]]). Native names and other aliases become '''redirects'''.
	* '''Categories''' follow real-encyclopedia habits but '''drop the global "of Yezur"''' — we would not write "Rivers of Earth", so we write [[:Category:Continents\|Continents]], not "Continents of Yezur". Keep narrower place qualifiers, such as "~~Polities of~~ Andusia".		* '''Categories''' follow real-encyclopedia habits but '''drop the global "of Yezur"''' — we would not write "Rivers of Earth", so we write [[:Category:Continents\|Continents]], not "Continents of Yezur". Keep narrower place qualifiers, such as "Countries in Andusia".
	* '''Templates, modules, and categories are in-character too.''' Avoid real-world terms in their names; encyclopedia-furniture words (Infobox, Cite, Stub, Navbox) are fine, since the in-world encyclopedia uses them about itself.		* '''Templates, modules, and categories are in-character too.''' Avoid real-world terms in their names; encyclopedia-furniture words (Infobox, Cite, Stub, Navbox) are fine, since the in-world encyclopedia uses them about itself.

Line 78:		Line 78:
	== Categories ==		== Categories ==

	Categories form a '''nested hierarchy''' — and, being a directed graph, a category may have more than one parent. Broad topics branch into specific sub-categories; a page joins the '''most specific''' categories that apply, not a flat top-level bucket. Entity-type categories nest inside topic branches: a country in Andusia sits in a "~~Polities of~~ Andusia" category that is a child of both "Andusia" and "~~Polities~~".		Categories form a '''nested hierarchy''' — and, being a directed graph, a category may have more than one parent. Broad topics branch into specific sub-categories; a page joins the '''most specific''' categories that apply, not a flat top-level bucket. Entity-type categories nest inside topic branches: a country in Andusia sits in a "Countries in Andusia" category that is a child of both "Andusia" and "Countries".

	Intersection categories are welcome wherever they aid navigation — "Former countries in Andusia" or "2002 deaths" are perfectly valid. Only hyper-specific slices no reader would browse — "polities in Andusia founded before a given year" — are left unbuilt: neither a category nor a list.		Intersection categories are welcome wherever they aid navigation — "Former countries in Andusia" or "2002 deaths" are perfectly valid. Only hyper-specific slices no reader would browse — "polities in Andusia founded before a given year" — are left unbuilt: neither a category nor a list.
Line 101:		Line 101:
	== Maps ==		== Maps ==

	Link to the Yezur map with <code><nowiki>{{Node}}</nowiki></code>, <code><nowiki>{{Way}}</nowiki></code>, and <code><nowiki>{{Relation}}</nowiki></code> (by object id), or <code><nowiki>{{Coords}}</nowiki></code> / <code><nowiki>{{Coordslink}}</nowiki></code> (by coordinates).		* Link to the Yezur map with <code><nowiki>{{Node}}</nowiki></code>, <code><nowiki>{{Way}}</nowiki></code>, and <code><nowiki>{{Relation}}</nowiki></code> (by object id), or <code><nowiki>{{Coords}}</nowiki></code> / <code><nowiki>{{Coordslink}}</nowiki></code> (by coordinates).
			* A subject that resolves to '''a single point''' on the map takes <code><nowiki>{{On the map\|lat\|lon}}</nowiki></code> ([[Template:On the map]]) on its first line: it places a link beside the page title rather than inline, and takes effect once per page — where it appears more than once, the '''last''' use wins. Continents and countries, which cannot be reduced to a single point, do not take it.

			== Files ==

			* '''Files are categorised''', like pages — a file joins the most specific categories that apply, and file categories are in-character like every other (see [[#Naming\|Naming]]). [[:Category:Files]] is the top-level container they hang from.
			* '''A source or licence line is recorded where one is needed.''' Where nothing outside the wiki places a condition on a file's use, none is written.

	== Sourcing ==		== Sourcing ==

Thiorosan: Record the Cargo ruling (2026-07-30): encyclopedia lists are hand-curated; Lexemes is the wiki's one remaining Cargo table

2026-07-30T11:27:19Z

Record the Cargo ruling (2026-07-30): encyclopedia lists are hand-curated; Lexemes is the wiki's one remaining Cargo table

← Older revision		Revision as of 11:27, 30 July 2026
Line 80:		Line 80:
	Categories form a '''nested hierarchy''' — and, being a directed graph, a category may have more than one parent. Broad topics branch into specific sub-categories; a page joins the '''most specific''' categories that apply, not a flat top-level bucket. Entity-type categories nest inside topic branches: a country in Andusia sits in a "Polities of Andusia" category that is a child of both "Andusia" and "Polities".		Categories form a '''nested hierarchy''' — and, being a directed graph, a category may have more than one parent. Broad topics branch into specific sub-categories; a page joins the '''most specific''' categories that apply, not a flat top-level bucket. Entity-type categories nest inside topic branches: a country in Andusia sits in a "Polities of Andusia" category that is a child of both "Andusia" and "Polities".

	Intersection categories are welcome wherever they aid navigation — "Former countries in Andusia" or "2002 deaths" are perfectly valid. Only hyper-specific slices no reader would browse — "polities in Andusia founded before a given year" — are ~~better answered by~~ a ~~'''Cargo query''' than by~~ a ~~category~~.		Intersection categories are welcome wherever they aid navigation — "Former countries in Andusia" or "2002 deaths" are perfectly valid. Only hyper-specific slices no reader would browse — "polities in Andusia founded before a given year" — are left unbuilt: neither a category nor a list.

	== Infoboxes and structured data ==		== Infoboxes and structured data ==
Line 87:		Line 87:
	* '''Prefer the more specific infobox''' when the subject warrants one — an orchestra is a valid case for a new infobox even where a broader musical-artist infobox already exists — but '''ask the operator before creating a new infobox''', as with categories.		* '''Prefer the more specific infobox''' when the subject warrants one — an orchestra is a valid case for a new infobox even where a broader musical-artist infobox already exists — but '''ask the operator before creating a new infobox''', as with categories.
	* Infoboxes render through the shared Lua module [[Module:Infobox]] and one stylesheet, [[Template:Infobox/styles.css]].		* Infoboxes render through the shared Lua module [[Module:Infobox]] and one stylesheet, [[Template:Infobox/styles.css]].
	* ~~Each infobox also files its facts into a~~ '''~~Cargo table~~'''~~, so lists~~, member rosters, and cross-references '''~~build~~ and ~~maintain themselves~~''' from the ~~articles~~.		* Infoboxes are '''display only''' — they file nothing into a database. Lists, member rosters, and cross-references are '''written and maintained by hand''', curated like any prose; the daily routine cross-checks them against the articles they summarise. (Cargo was retired from the encyclopedia in 2026-07: query-driven lists sat stale in the parser cache, could never show a page that did not yet exist, and read as machinery where an encyclopedia wants curation.)
	* '''~~Store plain values~~''' ~~in any field you will display in a Cargo query table~~: ~~Cargo prints raw~~ <code><nowiki>~~[[wikilinks]]~~</nowiki></code> ~~in query cells. Link entities in~~ the ~~prose or infobox instead~~.		* The '''one deliberate exception''' is the Dictionary: <code><nowiki>{{head}}</nowiki></code> files each entry into the '''Lexemes''' Cargo table — see [[Yezur Wiki:Dictionary structure]]. Any change to its schema needs a one-time administrative rebuild ("recreate data") on [[Template:Head]].
	* Adding a field to ~~a Cargo table changes~~ its schema~~, which~~ needs a one-time administrative rebuild ("recreate data") on ~~the template~~.

	== Open threads ==		== Open threads ==

Alompan: Drop the retired Family A-E placeholder bullet (flag 45a)

2026-07-28T20:10:09Z

Drop the retired Family A-E placeholder bullet (flag 45a)

← Older revision		Revision as of 20:10, 28 July 2026
Line 66:		Line 66:

	* '''Language articles''' use the "''X'' language" form (e.g. [[Gaillean language]]). Native names and other aliases become '''redirects'''.		* '''Language articles''' use the "''X'' language" form (e.g. [[Gaillean language]]). Native names and other aliases become '''redirects'''.
	* '''Language families''' currently carry placeholder labels ("Family A", and so on) until their in-world names are derived; use them sparingly.
	* '''Categories''' follow real-encyclopedia habits but '''drop the global "of Yezur"''' — we would not write "Rivers of Earth", so we write [[:Category:Continents\|Continents]], not "Continents of Yezur". Keep narrower place qualifiers, such as "Polities of Andusia".		* '''Categories''' follow real-encyclopedia habits but '''drop the global "of Yezur"''' — we would not write "Rivers of Earth", so we write [[:Category:Continents\|Continents]], not "Continents of Yezur". Keep narrower place qualifiers, such as "Polities of Andusia".
	* '''Templates, modules, and categories are in-character too.''' Avoid real-world terms in their names; encyclopedia-furniture words (Infobox, Cite, Stub, Navbox) are fine, since the in-world encyclopedia uses them about itself.		* '''Templates, modules, and categories are in-character too.''' Avoid real-world terms in their names; encyclopedia-furniture words (Infobox, Cite, Stub, Navbox) are fine, since the in-world encyclopedia uses them about itself.

Khurouan: Add Maintenance section: {{delete}} + deletion queue, Auphen errors

2026-07-18T15:26:30Z

Add Maintenance section: {{delete}} + deletion queue, Auphen errors

← Older revision		Revision as of 15:26, 18 July 2026
Line 95:		Line 95:

	Unresolved questions, placeholder names, and deliberate dangling references are recorded as plain text on the article's '''Talk''' page, under an <code><nowiki>== Open threads ==</nowiki></code> heading — never as hidden markers inside the article.		Unresolved questions, placeholder names, and deliberate dangling references are recorded as plain text on the article's '''Talk''' page, under an <code><nowiki>== Open threads ==</nowiki></code> heading — never as hidden markers inside the article.

			== Maintenance ==

			* '''Flagging for deletion.''' The editing bots hold no delete right, so pages awaiting removal are '''tagged, not deleted'''. Put <code><nowiki>{{delete\|reason}}</nowiki></code> ([[Template:Delete]]) on a page to show a deletion banner and file it into [[:Category:Pages flagged for deletion]] — the queue an administrator (Yezur) works through. Remove the tag to keep the page.
			* '''Auphen errors.''' Dictionary pages whose <code><nowiki>{{auphen}}</nowiki></code> pronunciation cannot be resolved collect in [[:Category:Auphen errors]] for review.

	== Maps ==		== Maps ==

Thiorosan: Add 'The Earth test' (qualify by planet only where Wikipedia would) and 'Text formatting' (Wikipedia's MoS applies; no bold for emphasis)

2026-07-17T10:28:04Z

Add 'The Earth test' (qualify by planet only where Wikipedia would) and 'Text formatting' (Wikipedia's MoS applies; no bold for emphasis)

← Older revision		Revision as of 10:28, 17 July 2026
Line 15:		Line 15:

	Yezur is not Earth. Do not invoke real civilizations, cultures, religions, writing systems, landmarks, or figures by their real-world names — no "Latin script", no "Romanized", no real place or people names. Analogy is welcome: monarchies, pottery, navigation, cathedrals and countless familiar concepts exist here in recognizable forms — but each should feel grown from Yezur's own history, not lifted from a specific real culture.		Yezur is not Earth. Do not invoke real civilizations, cultures, religions, writing systems, landmarks, or figures by their real-world names — no "Latin script", no "Romanized", no real place or people names. Analogy is welcome: monarchies, pottery, navigation, cathedrals and countless familiar concepts exist here in recognizable forms — but each should feel grown from Yezur's own history, not lifted from a specific real culture.

			=== The Earth test ===

			Write about Yezur the way Wikipedia writes about Earth: as ''the'' world, not ''a'' world. Wherever "Yezur" or "Yezuri" appears, the sentence should still read as a natural Wikipedia sentence with "Earth" in its place. Wikipedia's article on Basque does not say the language has "no clear cognates in any other Earth language" — so ours must not say "in any other Yezuri language". Qualify by planet only where Wikipedia would: "loanwords drawn from languages across Yezur" passes the test ("languages across Earth"); a reflexive "Yezuri" in front of every other noun does not.

	=== No magic ===		=== No magic ===
Line 65:		Line 69:
	* '''Categories''' follow real-encyclopedia habits but '''drop the global "of Yezur"''' — we would not write "Rivers of Earth", so we write [[:Category:Continents\|Continents]], not "Continents of Yezur". Keep narrower place qualifiers, such as "Polities of Andusia".		* '''Categories''' follow real-encyclopedia habits but '''drop the global "of Yezur"''' — we would not write "Rivers of Earth", so we write [[:Category:Continents\|Continents]], not "Continents of Yezur". Keep narrower place qualifiers, such as "Polities of Andusia".
	* '''Templates, modules, and categories are in-character too.''' Avoid real-world terms in their names; encyclopedia-furniture words (Infobox, Cite, Stub, Navbox) are fine, since the in-world encyclopedia uses them about itself.		* '''Templates, modules, and categories are in-character too.''' Avoid real-world terms in their names; encyclopedia-furniture words (Infobox, Cite, Stub, Navbox) are fine, since the in-world encyclopedia uses them about itself.

			== Text formatting ==

			Wikipedia's [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Text_formatting Manual of Style on text formatting] applies here, overwhelmingly. In particular:

			* '''Boldface''' marks the article's subject — and its significant alternative names and redirect targets — at first mention, and almost nothing else. Do '''not''' bold terms for emphasis.
			* ''Italics'' carry their usual duties: words as words, native-language forms, titles of works — and only sparing emphasis.

	== Categories ==		== Categories ==

Thiorosan: Soften 'Familiar to the second level': some things (sports especially) transfer essentially whole; what never transfers is the Earth-specific pedigree

2026-07-17T08:21:16Z

Soften 'Familiar to the second level': some things (sports especially) transfer essentially whole; what never transfers is the Earth-specific pedigree

← Older revision		Revision as of 08:21, 17 July 2026
Line 26:		Line 26:
	=== Familiar to the second level ===		=== Familiar to the second level ===

	Much of Yezur matches Earth '''up to the second-most specific level'''. The broad kinds are shared: there are zebras, though not Earth's zebra species; ~~there are many sports similar to Earth's, some all but identical, though never Earth's own; likewise~~ crops, instruments, institutions, dress. ~~However close the resemblance runs~~, the '''~~most~~ specific ~~level is always Yezur~~'~~s own~~''~~' — its own~~ species, ~~its own rules~~, its ~~own names~~ and history. This is the constructive side of [[#No real-world references\|no real-world references]]: ~~reach for~~ the familiar kind~~, one step above Earth's specific instance~~, and give Yezur its own.		Much of Yezur matches Earth '''up to the second-most specific level'''. The broad kinds are shared: there are zebras, though not Earth's zebra species; crops, instruments, institutions and dress all have close counterparts. Some things transfer essentially whole — many sports exist just as on Earth, at worst under mildly different rules or disciplines. What never transfers is the '''Earth-specific pedigree''': the exact species, the founding story, the name that honours an Earth place or person. However familiar the thing itself, its origin and history are Yezur's own. This is the constructive side of [[#No real-world references\|no real-world references]]: take the familiar kind, and give Yezur its own instance of it.

	=== Where out-of-frame content goes ===		=== Where out-of-frame content goes ===

Thiorosan: Add 'Familiar to the second level': Yezur matches Earth up to the second-most specific level; the most specific instance is always Yezur's own

2026-07-17T07:06:40Z

Add 'Familiar to the second level': Yezur matches Earth up to the second-most specific level; the most specific instance is always Yezur's own

← Older revision		Revision as of 07:06, 17 July 2026
Line 23:		Line 23:

	Biology, geology, and climate behave as in reality, and the cosmos is the real one; only the specifics — species, peoples, surface geography — are Yezuri.		Biology, geology, and climate behave as in reality, and the cosmos is the real one; only the specifics — species, peoples, surface geography — are Yezuri.

			=== Familiar to the second level ===

			Much of Yezur matches Earth '''up to the second-most specific level'''. The broad kinds are shared: there are zebras, though not Earth's zebra species; there are many sports similar to Earth's, some all but identical, though never Earth's own; likewise crops, instruments, institutions, dress. However close the resemblance runs, the '''most specific level is always Yezur's own''' — its own species, its own rules, its own names and history. This is the constructive side of [[#No real-world references\|no real-world references]]: reach for the familiar kind, one step above Earth's specific instance, and give Yezur its own.

	=== Where out-of-frame content goes ===		=== Where out-of-frame content goes ===

Thiorosan: Per operator: intersection categories welcome (Cargo only for hyper-specific slices); prefer specific infoboxes but ask before creating one; each agent edits through its own account

2026-07-16T12:29:45Z

Per operator: intersection categories welcome (Cargo only for hyper-specific slices); prefer specific infoboxes but ask before creating one; each agent edits through its own account

← Older revision		Revision as of 12:29, 16 July 2026
Line 66:		Line 66:
	Categories form a '''nested hierarchy''' — and, being a directed graph, a category may have more than one parent. Broad topics branch into specific sub-categories; a page joins the '''most specific''' categories that apply, not a flat top-level bucket. Entity-type categories nest inside topic branches: a country in Andusia sits in a "Polities of Andusia" category that is a child of both "Andusia" and "Polities".		Categories form a '''nested hierarchy''' — and, being a directed graph, a category may have more than one parent. Broad topics branch into specific sub-categories; a page joins the '''most specific''' categories that apply, not a flat top-level bucket. Entity-type categories nest inside topic branches: a country in Andusia sits in a "Polities of Andusia" category that is a child of both "Andusia" and "Polities".

	~~Do not manufacture a category for every possible intersection~~. ~~Build the main navigational branches; arbitrary~~ slices — "polities in Andusia founded before a given year" — are answered by a '''Cargo query''' ~~instead~~.		Intersection categories are welcome wherever they aid navigation — "Former countries in Andusia" or "2002 deaths" are perfectly valid. Only hyper-specific slices no reader would browse — "polities in Andusia founded before a given year" — are better answered by a '''Cargo query''' than by a category.

	== Infoboxes and structured data ==		== Infoboxes and structured data ==

	* Each entity type has '''its own infobox''', kept '''granular''': [[Template:Infobox former country]] is separate from the living-state [[Template:Infobox polity]], so each carries only the fields that matter to it.		* Each entity type has '''its own infobox''', kept '''granular''': [[Template:Infobox former country]] is separate from the living-state [[Template:Infobox polity]], so each carries only the fields that matter to it.
			* '''Prefer the more specific infobox''' when the subject warrants one — an orchestra is a valid case for a new infobox even where a broader musical-artist infobox already exists — but '''ask the operator before creating a new infobox''', as with categories.
	* Infoboxes render through the shared Lua module [[Module:Infobox]] and one stylesheet, [[Template:Infobox/styles.css]].		* Infoboxes render through the shared Lua module [[Module:Infobox]] and one stylesheet, [[Template:Infobox/styles.css]].
	* Each infobox also files its facts into a '''Cargo table''', so lists, member rosters, and cross-references '''build and maintain themselves''' from the articles.		* Each infobox also files its facts into a '''Cargo table''', so lists, member rosters, and cross-references '''build and maintain themselves''' from the articles.
Line 90:		Line 91:
	== Notes for AI agents ==		== Notes for AI agents ==

	Agents run locally and ~~edit through~~ the ~~Khurouan account~~. Additional operating context — the project setup, the who-edits-as-whom rule, and this convention set — lives in ~~the project~~'s <code>CLAUDE.md</code>. Always read the relevant page(s) before asserting canon, and surface every write you make.		Agents run locally, '''each editing through its own account''' — [[User:Khurouan\|Khurouan]] and [[User:Thiorosan\|Thiorosan]] for the interactive workstations, [[User:Alompan\|Alompan]] for the daily routine. The agent accounts are gathered in [[:Category:Agent accounts]]. Additional operating context — the project setup, the who-edits-as-whom rule, and this convention set — lives in each workstation's <code>CLAUDE.md</code>. Always read the relevant page(s) before asserting canon, and surface every write you make.

	[[Category:Yezur Wiki]]		[[Category:Yezur Wiki]]

Khurouan: Add the full editor roster

2026-07-15T20:41:19Z

Add the full editor roster

← Older revision		Revision as of 20:41, 15 July 2026
Line 46:		Line 46:
	== Who edits as whom ==		== Who edits as whom ==

	* '''Yezur''' is the human editor, working in the browser.		Every editor has a distinct account, so authorship is clear at a glance in page history:
	* '''[[User:Khurouan\|Khurouan]]''' is the ~~AI author~~; ~~every AI~~ edit ~~goes through this account, so authorship is clear at a glance in page history~~.		* '''Yezur''' — the human editor, working in the browser.
			* '''[[User:Khurouan\|Khurouan]]''' and '''[[User:Thiorosan\|Thiorosan]]''' — interactive AI authors, the same role from different workstations; separate accounts so an edit can be traced to the agent that made it.
			* '''[[User:Alompan\|Alompan]]''' — the automated daily-maintenance routine (see [[Yezur Wiki:Daily routine]]).

			(The bot accounts share their names with the ancient cities of [[Hertia]].)

	Keep '''edit summaries in-character''' where you reasonably can — describe the change to the article ("Start an article on the Hertic language"), not the process behind it.		Keep '''edit summaries in-character''' where you reasonably can — describe the change to the article ("Start an article on the Hertic language"), not the process behind it.

Khurouan: Create the wiki conventions and onboarding guide

2026-07-15T19:38:44Z

Create the wiki conventions and onboarding guide

New page

This page collects the editorial and structural conventions of the '''Yezur Wiki''' — a working reference for new editors, human and AI alike. The wiki is the single source of truth for the world of Yezur; these are the habits that keep it consistent.

== The cardinal rule ==

A fact is '''canon only once it is written onto a wiki page'''. Conversation, agreement, and brainstorming are not canon until they land here.

== Editorial voice ==

Articles in the main namespace are written as an '''encyclopedia by Yezuri, for Yezuri readers'''. Two requirements, always together:

* '''Encyclopedic register.''' Neutral and third-person, definition-first, like any good reference work. No storytelling, no chatty asides, no first- or second-person address to the reader, no marketing or how-to tone.
* '''In-world (Watsonian) frame.''' Written from inside Yezur. Never break frame: no comparisons to the real world, no asides to the real reader, no mention of the design process or the tools used to build the wiki.

=== No real-world references ===

Yezur is not Earth. Do not invoke real civilizations, cultures, religions, writing systems, landmarks, or figures by their real-world names — no "Latin script", no "Romanized", no real place or people names. Analogy is welcome: monarchies, pottery, navigation, cathedrals and countless familiar concepts exist here in recognizable forms — but each should feel grown from Yezur's own history, not lifted from a specific real culture.

=== No magic ===

No supernatural forces or spellcraft act on the physical world. In-world myths and folk beliefs may exist without being literally true.

=== Plausible mechanics ===

Biology, geology, and climate behave as in reality, and the cosmos is the real one; only the specifics — species, peoples, surface geography — are Yezuri.

=== Where out-of-frame content goes ===

Real-world commentary — design rationale, comparisons, notes on tooling, unresolved questions — never appears in article text. It belongs on '''Talk''' pages, in the '''Meta:''' namespace, or in this '''Yezur Wiki:''' namespace.

== Namespaces ==

{| class="wikitable"
! Namespace !! Frame !! Purpose
|-
| (Main), '''Dictionary:''', '''Map:''' || In-character || Encyclopedia articles, the dictionary, and the map wiki
|-
| '''Yezur Wiki:''' || Out-of-frame || Policy, style, and conventions (this page)
|-
| '''Meta:''' || Out-of-frame || Design notes and rationale
|-
| '''Talk:''' (all) || Out-of-frame || Discussion and open threads
|}

Rule of thumb: '''everything a reader or editor sees is in-character''', except the Meta:, Talk:, and Yezur Wiki: namespaces. That includes template, module, and category names — see [[#Naming|Naming]].

== Who edits as whom ==

* '''Yezur''' is the human editor, working in the browser.
* '''[[User:Khurouan|Khurouan]]''' is the AI author; every AI edit goes through this account, so authorship is clear at a glance in page history.

Keep '''edit summaries in-character''' where you reasonably can — describe the change to the article ("Start an article on the Hertic language"), not the process behind it.

== Naming ==

* '''Language articles''' use the "''X'' language" form (e.g. [[Gaillean language]]). Native names and other aliases become '''redirects'''.
* '''Language families''' currently carry placeholder labels ("Family A", and so on) until their in-world names are derived; use them sparingly.
* '''Categories''' follow real-encyclopedia habits but '''drop the global "of Yezur"''' — we would not write "Rivers of Earth", so we write [[:Category:Continents|Continents]], not "Continents of Yezur". Keep narrower place qualifiers, such as "Polities of Andusia".
* '''Templates, modules, and categories are in-character too.''' Avoid real-world terms in their names; encyclopedia-furniture words (Infobox, Cite, Stub, Navbox) are fine, since the in-world encyclopedia uses them about itself.

== Categories ==

Categories form a '''nested hierarchy''' — and, being a directed graph, a category may have more than one parent. Broad topics branch into specific sub-categories; a page joins the '''most specific''' categories that apply, not a flat top-level bucket. Entity-type categories nest inside topic branches: a country in Andusia sits in a "Polities of Andusia" category that is a child of both "Andusia" and "Polities".

Do not manufacture a category for every possible intersection. Build the main navigational branches; arbitrary slices — "polities in Andusia founded before a given year" — are answered by a '''Cargo query''' instead.

== Infoboxes and structured data ==

* Each entity type has '''its own infobox''', kept '''granular''': [[Template:Infobox former country]] is separate from the living-state [[Template:Infobox polity]], so each carries only the fields that matter to it.
* Infoboxes render through the shared Lua module [[Module:Infobox]] and one stylesheet, [[Template:Infobox/styles.css]].
* Each infobox also files its facts into a '''Cargo table''', so lists, member rosters, and cross-references '''build and maintain themselves''' from the articles.
* '''Store plain values''' in any field you will display in a Cargo query table: Cargo prints raw <code><nowiki>[[wikilinks]]</nowiki></code> in query cells. Link entities in the prose or infobox instead.
* Adding a field to a Cargo table changes its schema, which needs a one-time administrative rebuild ("recreate data") on the template.

== Open threads ==

Unresolved questions, placeholder names, and deliberate dangling references are recorded as plain text on the article's '''Talk''' page, under an <code><nowiki>== Open threads ==</nowiki></code> heading — never as hidden markers inside the article.

== Maps ==

Link to the Yezur map with <code><nowiki>{{Node}}</nowiki></code>, <code><nowiki>{{Way}}</nowiki></code>, and <code><nowiki>{{Relation}}</nowiki></code> (by object id), or <code><nowiki>{{Coords}}</nowiki></code> / <code><nowiki>{{Coordslink}}</nowiki></code> (by coordinates).

== Sourcing ==

Cite sources with <code><nowiki><ref>...</ref></nowiki></code>, collected by a <code><nowiki><references /></nowiki></code> tag in a references section.

== Notes for AI agents ==

Agents run locally and edit through the Khurouan account. Additional operating context — the project setup, the who-edits-as-whom rule, and this convention set — lives in the project's <code>CLAUDE.md</code>. Always read the relevant page(s) before asserting canon, and surface every write you make.

[[Category:Yezur Wiki]]