Jump to content

Yezur Wiki:Daily routine/Report

From Yezur Wiki
< Yezur Wiki:Daily routine
Revision as of 20:13, 27 July 2026 by Alompan (talk | contribs) (Daily maintenance report 2026-07-27: 0 verdicts pending; five new findings from the first file upload and the Tacchoan expansion)

Working report of the Alompan daily routine (how it works). Every finding lives as one row below until it is resolved: set a row's Status to give a verdict, and the next run carries it out and clears the row. Nothing on the wiki is changed except what is explicitly approved or amended.

The possible statuses:

  • pending — awaiting review; no action is taken (the default)
  • approved or accepted — carry out the Suggested fix, as written
  • amended — carry out the fix described in Notes instead
  • deferred — real, but not now; moves to Dismissed flags and is not re-flagged
  • rejected — not an issue; moves to Dismissed flags and is not re-flagged
  • to to-do — real issue that should be marked on User talk:Yezur's to-do list instead for human intervention
  • fixed — real issue, but was a simple fix for Yezur, and has been taken care of; confirm and clear

To revive a dismissed flag, move it back into the table as pending.

Flagged items

# Flagged Type Severity Page(s) Issue Suggested fix Status Notes
22 2026-07-19 structured data resolved Special:CargoTables — Lexemes Resolved — no action needed. The Lexemes Cargo table has finished draining and is fully in sync: 526 of 526 rows. The per-language split totals correctly — Ancient Hertic 212, Proto-Herta-Olaic 211, Proto-Njeshan 102, Pjany 1. No administrator intervention was needed at any point. none — the row is kept only so the resolution is recorded; clear it with fixed or rejected. pending Re-confirmed 2026-07-26 by re-querying the table end to end (two pages, offset 0 and 500): 526 rows, split Ancient Hertic 212 / Proto-Herta-Olaic 211 / Proto-Njeshan 102 / Pjany 1. Job queue still 0. Ran its full course over three runs — 177 → 521 → 526 — and has now held unchanged for three more. Severity retired; the row waits only on a verdict to clear it.
23 2026-07-19 structural medium Category:Dictionary templates Wanted category with 7 members. The Dictionary's template set categorises into it — including Template:Etym-missing — but the category page does not exist. Its two sibling template categories, Category:Link templates and Category:Infobox templates, both exist and both sit under Category:Templates. Create it on the sibling pattern: a one-line description (Templates used by the Yezur Dictionary.) plus [[Category:Templates]]. Mechanical; the parent is unambiguous. pending Still wanted, with 7 members, on 2026-07-26. All 25 templates were re-listed this run and the seven hold by name: Etym-missing, Head, Lb, the three declension wrappers and decl/core. The oldest unresolved mechanical fix in the table, now seven runs old.
24 2026-07-19 structural low Category:Ancient Hertic entries needing etymology Uncategorised category. Created alongside Template:Etym-missing, which files entries into it as a review queue. It has no parent, so it hangs off the category tree entirely — and it is the first of a per-language series (Category:<Language> entries needing etymology) that the template will generate for every language it is used with. Give it a parent, and settle the pattern once for the whole series. Best guess: Category:Yezur Wiki, the existing project/maintenance container. Cleaner alternative, if you would rather keep housekeeping queues separate from project pages: create Category:Dictionary maintenance (or a broader Category:Tracking categories) under Category:Yezur Wiki and parent this and its future siblings there. Say which and it can be applied mechanically. pending Still uncategorised on 2026-07-26, holding the same three members (Dictionary:νηεν, Dictionary:φτι, Dictionary:ω) — cross-checked this run from the other direction, since {{etym-missing}} is transcluded by exactly three Dictionary pages and no others. See #27 and #44: one parent decision would settle four maintenance categories at once, two that are missing and two that are misfiled. Its name is also caught up in #36.
25 2026-07-19 structural low Module:Auphen, Module:Auphen/frame, Module:Auphen/YAQ-HE, Module:Auphen/YBS-PJ, Module:Head, Module:Labels, Module:Languages Wanted documentation subpages. Seven modules carry a documentation transclusion whose /doc page does not exist, so each renders a redlinked doc box. This is the same gap as #9 last run, which was approved and filled by Module:Infobox/doc. Create each /doc on the Module:Infobox/doc pattern, restating only what the module source itself establishes — purpose, entry points, parameters — and inventing no behaviour. Module:Auphen/YAQ-HE and Module:Auphen/YBS-PJ are data pages and need only a short note on the ruleset each holds. Best done by Khurouan, who wrote the modules, but Alompan can do it from the source on approval. pending All seven still wanted on 2026-07-26 — and all nine modules were read in full this run, the first such sweep, so the material for each /doc is now in hand: Module:Auphen states its own API contract in its header, Module:Auphen/frame has two entry points (auphen and raw), Module:Head, Module:Labels and Module:Languages each carry a worked invoke signature per function, and the two data pages hold four documented keys apiece. Settle #48, #49 and #50 first: all three came out of the same reading, and all three are corrections the /doc pages should not inherit. Module:Languages still best left last, or after #36.
26 2026-07-19 structural high Map:Conventions, Map:Features Wanted pages linked from a portal front page — and now the only route into 33 live pages. Map:Main Page is built around two navigation cards — "Map features" (the keys and values that describe things on the map) and "Conventions" (how features are tagged, named, and classified) — and both targets are redlinks. Those two links are the only links Map:Main Page carries, so with 33 key and value pages now in the namespace, the whole documented tag set is unreachable from the portal meant to index it. flag-only on the substance — how the map is actually tagged is your side of the work, and the routine will not invent map conventions. What is now mechanical, if you want it: Map:Features could be built as a plain index of the 33 pages that exist, grouped by key, making no new claims. Say the word and that much can be done. pending Re-checked 2026-07-26, unchanged, and still the table's only high-severity row: 33 pages, none of them reachable from the portal that exists to index them. Both targets still carry two inbound links each and no page.
27 2026-07-20 structural low Category:Hidden categories, Category:Auphen test failures Two maintenance/tracking categories that are linked but do not exist. (a) Category:Hidden categories — the standard container into which any __HIDDENCAT__ category files itself; it currently holds one member, Category:Auphen errors, but the container page itself is missing. (b) Category:Auphen test failures — linked from Template:Auphen/testcases as the bin for failing test cases; empty right now (no tests are failing, which is the good state), so it shows only as a redlink in the test harness. Neither is content; both are housekeeping furniture, and both are homeless in the same way as #24. Settle the maintenance-container question once (see #24: Category:Yezur Wiki directly, or a new Category:Tracking categories beneath it) and create all three there. Category:Hidden categories should itself carry __HIDDENCAT__ and a one-line description; Category:Auphen test failures should mirror the existing Category:Auphen errors. Mechanical once the parent is chosen. pending Filed with #24 deliberately, and #44 now joins them: the same one decision resolves the etymology-queue series, this hidden-categories container, the Auphen test-failure bin, and the two existing maintenance categories presently misfiled under Category:Templates. Re-checked 2026-07-26 — (b) is still correctly empty: Template:Auphen/testcases was read again and its four Pjany rows still pass. It shows in Special:UnusedTemplates only because a testcases page is transcluded nowhere, which is the right state and not a finding.
28 2026-07-21 naming medium High Nichana, Otjesi, Pises Three language articles are not at the conventional title. Conventions set the form "X language" for language articles, and every other language on the wiki follows it — Gaillean language, Hertic language, Lonish language, Nichana language, Pjany language, Uu language, English language. The three attested medieval stages of Njeshan are the only exceptions: they sit at the bare name. (The bare form is correct for the families — Njeshan, Herta-Olaic, Tacchoan — which is a separate case.) Move each to the conventional title, leaving the bare name behind as a redirect: High Nichana to High Nichana language, Otjesi to Otjesi language, Pises to Pises language. All three target titles are free, and each article has only two inbound links (its family page Njeshan and its descendant language), which can be repointed at the same time. Mechanical; the convention is explicit. pending Re-confirmed still open 2026-07-26; all three target titles are still free and each article still has the same two inbound links. Related to #29 — the same three pages, two independent fixes. Note that three rows now bear on §Naming — this one, #45(a) and the new #51 — so if more than one is approved they should be made in a single edit to that section.
29 2026-07-21 structured data medium High Nichana, Otjesi, Pises Three language articles carry no {{Infobox language}}, so they are absent from the Languages Cargo table. The table holds 7 rows; these three are not among them. The consequence is visible on Njeshan: its Members Cargo query lists only the four modern languages, and the three medieval stages have to be named in a prose sentence beneath the table instead. Every other language article on the wiki carries the infobox. Add {{Infobox language}} to each, filling only the fields the article itself already asserts — family=Njeshan and era=Medieval — and leaving native_name, region and code blank rather than inventing them. Each article states its family and its medieval status in its first sentence, so nothing new is asserted. Once the rows land, the prose sentence on Njeshan can be trimmed to whatever it still adds (the ancestor-of relationships, which the table does not carry). Note: era=Medieval is a value the table has not held before (Gaillean and Hertic are Ancient, the rest Modern); no schema change is involved. pending Re-confirmed still open 2026-07-26 — Languages still returns 7 rows. One of three rows on the same theme, worth reading together: #29 articles with no infobox, #41 the same shape one namespace over, and #43 a template whose infobox is filled in but whose table was never created. Distinct from dismissed #11 and from #37.
30 2026-07-21 open thread low User:Yezur An unfinished sentence, saved as the whole page. User:Yezur was created with a single line — "The name of a large Tacchoan city is ." — which breaks off where the name should be. No Tacchoan city is named anywhere on the wiki, and Taccho has no settlement articles, so nothing else supplies the missing word. Most likely an accidental save; possibly a note-to-self, or a naming prompt left for an author account. flag-only — the routine does not edit another editor's user page. Raised only so an unfinished line is not left standing. If it was meant as a naming prompt, say so and Khurouan can generate a spread of candidate Tacchoan city names to cull from; the routine will not invent one. pending Unchanged 2026-07-26; the page still holds nothing but that one broken-off line, saved 2026-07-21.
31 2026-07-22 structural medium Category:Map documentation Wanted category with 33 members — every page of the new Map tag set. All 33 key and value pages added to the Map: namespace on 2026-07-22 end with [[Category:Map documentation]], but the category page does not exist, so each shows a redlinked category and the set has no category-level index. It is by far the largest wanted category on the wiki outside the lexical backlog. Create it with a one-line description and a parent. Recommended parent: Category:Yezur, the root container, as a sixth top-level branch beside Geography, History, Languages and Templates — the Map: namespace is in-character per Conventions, so it should not hang under Category:Yezur Wiki, which its own page defines as "out-of-frame — about the wiki, not about the world." Alternative, if you would rather it sat a level down: create Category:Map under Category:Yezur and parent this beneath it, leaving room for other map categories later. Mechanical once you pick. pending Unchanged 2026-07-26 — still 33 members, still the largest wanted category outside the lexical backlog. Distinct from #24/#27/#44, which concern maintenance containers; this one is content documentation and does not wait on that decision.
32 2026-07-22 open thread medium Map:name The worked example cites a language and a language code that exist nowhere on the wiki. Map:name says additional names go in name:<lang>=* "using Yezur's language codes (for example name:yas-ai for Airananwe)". There is no Airananwe on the wiki — no article, no redirect, no page title beginning "Air", and no such row in the Languages or LanguageFamilies Cargo tables (the five families are Andusian, Herta-Olaic, Njeshan, Shung-Worrehan, Tacchoan). Nor does yas-ai fit the code registry: every registered code is uppercase on a YAQ-/YAP-/YBS-/YBP-/YXS- stem. The same sentence's other example, name:en, is likewise not the registered code for English, which the table holds as YXS-EN, YXS-NE. flag-only on the first half, mechanical on the second. (a) Say whether Airananwe is meant to be a Yezur language at all — the name reads as belonging to a neighbouring project rather than to this wiki, which is out of scope here. If it is not Yezuri, swap the example for an attested language and its registered code (name:YBS-PJ for Pjany, say). If it is Yezuri, it needs an article and a Languages row before the map documentation can lean on it. (b) Either way, reconcile the case: if the map really uses short lowercase codes rather than the wiki's registry codes, that mapping should be stated on Map:name itself, since the page currently claims the codes are Yezur's language codes. pending Unchanged 2026-07-26. Flagged rather than fixed because only you can say where Airananwe belongs; the routine will not invent a language or a code. Module:Languages was read in full this run and the registry holds exactly ten codes, every one uppercase on a YAQ-/YAP-/YBS-/YBP-/YXS- stem — no lowercase form among them and no yas- stem anywhere.
33 2026-07-22 structural low Map:place=hamlet, Map:place=suburb Two of the five values in a value table have no page. Map:place tabulates the settlement hierarchy as city / town / village / hamlet / suburb and links each; the first three exist, the last two are redlinks. They are the only redlinked values in any of the key pages' value tables — every other tabulated value (highway ×4, natural ×4, waterway ×2, landuse ×2, boundary ×1, railway ×1) has its page. Create the two on the pattern of Map:place=village, restating only what Map:place already says — hamlet: a very small cluster of dwellings with few or no services; suburb: a named district within a larger city or town — plus the usual tagging line and See also. Nothing new is asserted; the definitions are lifted from the parent page. Mechanical. pending Unchanged 2026-07-26, and still the only two redlinked values in any key page's value table. Narrower than #26: this completes a set that already defines itself, rather than writing map conventions.
34 2026-07-22 factual low Map:wiki The page's worked example is self-defeating and points at a page that does not exist. Map:wiki illustrates that spaces and underscores are interchangeable in a page title with: "so wiki=Khurouan and wiki=Khurouan reach the same page" — the two sides are identical, so the sentence demonstrates nothing; the underscore form was evidently lost. Separately, Khurouan is not an article: the ancient city is Khurou, and Khurouan is the name of an editing account (User:Khurouan), which makes it doubly ill-suited as the example of a map-to-article cross-reference. Rewrite the example around a real two-word title so the point survives — e.g. "so wiki=Sea of Sihia and wiki=Sea_of_Sihia reach the same page", using Sea of Sihia, which exists. Mechanical, one sentence. pending Unchanged 2026-07-26; Sea of Sihia re-confirmed to exist. Sharpened this run: Khurouan is not merely absent as an article — Khurou is itself a redirect to Hertia, as are Thiorosirega and Phose Serou, so Alompe is the only ancient city with an article of its own, and it is a single word too. Sea of Sihia remains the natural choice. One of a family of stale worked examples now in the table — see #45(b), #48, #49 and #52.
35 2026-07-22 convention low Map:boundary, Map:highway, Map:highway=motorway, Map:name, Map:place, Map:place=city Reflexive "on Yezur" in the new Map pages trips the Earth test. Conventions ask that every Yezur/Yezuri still read naturally with the real world's name swapped in, and warn specifically against a reflexive qualifier "in front of every other noun". Seven sentences in the new set do not survive the swap: "On Yezur the common case is the administrative hierarchy"; "Yezur's route network"; "the highest-capacity roads on Yezur"; "Almost everything named on Yezur takes a name=*"; "the points and areas that carry Yezur's place names"; "its standing on Yezur rather than a fixed population cut-off"; "the largest and most prominent settlements on Yezur". A tagging guide for the world's own map has no more need of the qualifier than a road atlas does. Delete the qualifier in those seven places, leaving the sentences otherwise untouched ("The common case is the administrative hierarchy", "the route network", "the highest-capacity roads", and so on). The other three Yezur mentions in the set are genuinely contrastive and should stay: "a Yezur convention" (Map:admin level), "Yezur's language codes" (Map:name) and "Yezur's own cross-reference; there is no link to any outside wiki" (Map:wiki). Mechanical, but it is a copyedit of your own new prose, so it wants your say-so. pending Unchanged 2026-07-26. Low severity — style polish, not an error. Deliberately not flagged alongside it: the imperative "How to tag" voice throughout the set, which is proper to a tagging guide and not the article-namespace register the convention governs. See #38: the article namespace carries 21 more instances of the same pattern, so whatever verdict this row gets should carry over to that one.
36 2026-07-23 naming medium Module:Languages, Hertic language, Category:Ancient Hertic entries needing etymology, the Dictionary One language goes by two names, and the two namespaces disagree. The article side calls it Hertic: the page is Hertic language, its infobox reads name=Hertic, Herta-Olaic names it "the ancient Hertic … language", and Dictionary:Main Page itself links it as "Hertic". The Dictionary side calls it Ancient Hertic: Module:Languages maps YAQ-HE to name = "Ancient Hertic", so every entry heads its section ==Ancient Hertic== (for example Dictionary:αβισι), all 212 of its Lexemes rows carry Ancient Hertic as their language name, and Module:Head builds its categories from the same string — ten of the wiki's 46 wanted categories are Category:Ancient Hertic …, alongside the existing Category:Ancient Hertic entries needing etymology. Neither Ancient Hertic nor Ancient Hertic language exists as a page or a redirect, so the Dictionary's own section heading leads nowhere from the encyclopedia side. Module:Languages is inconsistent with itself about it too: its header calls the table "the wiki's language-code registry … Keep this table in step with the Languages Cargo table", and its worked example a few lines below reads {{#invoke:Languages|name|YAQ-HE}} → Hertic, which is not what the table returns. A decision, then a mechanical fix — and it is worth deciding before the lexical categories are created (to-do flag #18), because Module:Head generates those names from this string, and creating 43 categories under the losing name means moving them all afterwards. Two clean ways out, each a one-line change: (a) settle on Hertic — change name and section for YAQ-HE in Module:Languages; the Dictionary headings, the Lexemes rows and every generated category follow automatically, and Category:Ancient Hertic entries needing etymology is moved to match. (b) settle on Ancient Hertic — keep the registry as it is and create Ancient Hertic as a redirect to Hertic language so the heading resolves; the article's name= field would then want changing to match. One reading to rule out first: if Hertic and Ancient Hertic are meant to be a language and a distinct earlier stage of it, then the wiki is simply missing whichever of the two has no article, and this becomes a content task rather than a rename. pending Re-confirmed 2026-07-26 from the module side, Module:Languages having been read in full: the mismatch is internal and exact — the registry line for YAQ-HE sets name = "Ancient Hertic", while the worked example in the comment above p.name, twenty lines below it, reads {{#invoke:Languages|name|YAQ-HE}} → Hertic. That comment is wrong about the table it sits in whichever name eventually wins, so it wants correcting either way. All 212 entries head ==Ancient Hertic==, with no exception. Does not block #42.
37 2026-07-23 structured data low Module:Languages, Special:CargoTables — Languages Two registered language codes back 313 of the Dictionary's 526 entries but have no article and no Languages row. Module:Languages registers ten codes; the Languages Cargo table holds seven rows. The gap is YAP-XX Proto-Herta-Olaic (211 Lexemes rows) and YBP-XX Proto-Njeshan (102) — together the majority of the Dictionary — and neither has a page: Proto-Herta-Olaic and Proto-Njeshan are both missing, as are the other three families' protos. The tenth code, YXS-NE New English, is properly accounted for: the registry deliberately files it under the English section, and English language's row carries both codes. The proto-languages are not simply forgotten — Module:Languages marks them recon = true and stars their forms, the LanguageFamilies table carries each family's proto as text ("Proto-Herta-Olaic (reconstructed)"), and Herta-Olaic states in prose that it has been reconstructed. Nothing is broken either: {{m|YAP-XX|…}} links word-to-word into the correct Dictionary section, exactly as designed. flag-only — whether a reconstructed language gets its own article is an editorial call, and the routine will not create one. Raised only because Module:Languages sets the invariant itself ("Keep this table in step with the Languages Cargo table") and two of its ten codes stand outside it; better to record that as deliberate than to leave it looking like drift. If proto-languages should stay as prose on the family pages, dismiss this and later runs will not re-open it. If they should become articles, that is five pages (Proto-Herta-Olaic, Proto-Njeshan, Proto-Andusian, Proto-Shung-Worrehan, Proto-Tacchoan) and a decision on whether the "X language" naming convention applies to a reconstruction. pending Re-confirmed 2026-07-26; the five proto names are deliberately unlinked here. The invariant this row turns on was read at source this run — it is line 9 of Module:Languages, "Keep this table in step with the Languages Cargo table" — and two of its ten codes stand outside a seven-row table. Strengthened by the Dictionary reading: 208 of the 209 written etymologies name Proto-Herta-Olaic, so the language with no article is the most-cited language in the Dictionary. Close in spirit to dismissed #11.
38 2026-07-24 convention medium Andusia, Andusian, Gaillean language, Herta-Olaic, Hertic language, Ignusia, Lonish language, Lovvocia, Nichana language, Njeshan, Pjany language, Shung-Worrehan, Sihia, Taccho, Tacchoan, Uu language, Vetsia, Vetsihia Reflexive "Yezuri" runs through the article namespace — 21 sentences across 18 pages. The same pattern as #35, found on the first full read of the main namespace. Conventions warn against "a reflexive 'Yezuri' in front of every other noun". It falls into two clusters. (a) The family formula, eleven pages — "one of the five major Yezuri language families" (Andusian, Herta-Olaic, Njeshan, Shung-Worrehan, Tacchoan); "Three of the five major Yezuri language families are native to …" (Andusia, Ignusia); "none of the five major Yezuri language families is native here" (Lovvocia, Sihia, Vetsia); "the sole major Yezuri language family" (Taccho). (b) Ten single instances — "is an ancient Yezuri language of Herta-Olaic" (Gaillean language, Hertic language); "is a Yezuri language of Njeshan" (Lonish language, Nichana language, Pjany language, Uu language); "the source language for Yezuri scientific binomials" (Gaillean language); "where the majority of Yezuri history has unfolded" (Ignusia); "where the tallest Yezuri mountains rise" (Taccho); "Yezuri geography treats them as separate continents" (Vetsihia). Delete the word in most of the 21 places ("is a language of Njeshan", "for scientific binomials"), and recast the four where deletion would cost the sense: "one of the world's five major language families" and its three variants; "where the majority of the world's history has unfolded"; "where the tallest mountains on Yezur rise" (that form passes — a real encyclopedia does write the highest mountain on Earth); "geographers treat them as separate continents". Explicitly not touched, and listed so the copyedit does not overreach: the continent lead sentences and infobox location fields (recorded as passing); "loanwords drawn from languages across Yezur" (English language) and "natural-science naming across Yezur" (Gaillean language), which are the exact shape Conventions cite as passing; and the Main Page framing lines, which are portal furniture rather than article prose. pending Unchanged 2026-07-26. Same class as #35 and should take the same verdict — filed separately only because this is older article prose rather than the new Map set, and because it is much the larger half: 21 instances against seven. Mechanical once decided.
39 2026-07-24 structural low Alompe A page filed in both a category and that category's own child. Alompe ends with [[Category:Cities in Hertia]] and [[Category:Ancient cities in Hertia]], and the second is a subcategory of the first — Category:Ancient cities in Hertia carries both Category:Ancient cities and Category:Cities in Hertia. Conventions ask a page to join "the most specific categories that apply", so the parent membership is redundant. Alompe is the only member of either category, so Category:Cities in Hertia presently exists to hold one page that its own child already holds. Remove [[Category:Cities in Hertia]] from Alompe and leave the ancient-cities line. One line, and the path Category:Cities → Category:Cities in Hertia → Category:Ancient cities in Hertia → Alompe stays unbroken. Mechanical. pending Unchanged 2026-07-26, and still the only page-level categorisation error on the wiki, with #44 still the only category-level one. Category:Cities in Hertia was re-read this run and does carry Category:Cities, so the chain Category:Cities → Category:Cities in Hertia → Category:Ancient cities in Hertia → Alompe survives the removal intact.
40 2026-07-24 convention low Pandenica, Vetsia The far-southern polar continent is described as "arctic". Pandenica opens "Pandenica is Yezur's arctic continent, in the planet's far south" and its infobox reads location=Far south of Yezur (arctic); Vetsia speaks of "the arctic continent Pandenica". The word carries a northern sense that the same sentence then contradicts in its next clause, and by the Earth test no encyclopedia calls its southern polar continent the arctic one. It is also the one place in the main namespace where a real-world regional name is standing in for a climate term, against no real-world references. Recast on polar, which is directionless and already the standard register: "Pandenica is Yezur's polar continent, in the planet's far south", location=Far south of Yezur (polar), and "the polar continent Pandenica". Three edits of one word each, and nothing else in either article changes. If Yezur should instead have its own paired names for the two polar regions, that is a naming decision and the routine will not invent one. pending Unchanged 2026-07-26; the arctic wording is still live in the Continents table's location field for Pandenica, so the fix should touch the infobox as well as the prose. Checked and deliberately not flagged beside it: taiga on Lovvocia, a biome term rather than a place name.
41 2026-07-24 structural low Betonia, Unteria, Sea of Sihia, Vetsihia The four geography articles that are not continents sit in the root bucket, and two of them reach no Cargo table. Category:Geography holds three subcategories (Cities, Continents, Countries) and four articles filed directly in it: Betonia and Unteria, the two named subcontinents of Andusia; Sea of Sihia, the wiki's only sea; and Vetsihia. Conventions ask a page to join "the most specific categories that apply, not a flat top-level bucket", and no narrower category exists for an island, a sea, or a subcontinent. Separately, Betonia and Unteria carry no infobox at all and so reach no Cargo table — where Vetsihia, which is not a continent either, does carry one (type=Geographic region (colloquial)). Template:Infobox continent documents its own scope as "a continent or major landmass", which a landmass "roughly half Andusia's size" plainly meets. Two halves; only the second is mechanical. (a) The categories want a decision, since creating one is your call: the natural set is Category:Seas and Category:Islands — or a single broader Category:Landforms — beneath Category:Geography, with Vetsihia arguably staying where it is as a region rather than a landform. Name them and they can be created and applied. (b) On approval, add {{Infobox continent}} to Betonia and Unteria filling only what each article's own first sentence asserts — type=Subcontinent and location=West of Andusia / Southeast of Andusia — and leaving adjacent, native_families and map_node blank rather than inventing them. Two notes: type defaults to Continent when omitted, so it must be given explicitly; and Category:Geography's own query filters on type='Continent', so it would be unaffected either way. pending Unchanged 2026-07-26; Category:Geography's Cargo query still filters on type='Continent'. The same shape as #29 one namespace over. Worth pairing with (a): Talk:Andusia, read this run, records both Betonia and Unteria as placeholder names "awaiting a Yezuri derivation" — so if the two are renamed later, a category created now under either name would need moving. The two halves can still be approved separately.
42 2026-07-25 structured data medium the Dictionary (209 entries), Template:Head, Special:CargoTables — Lexemes 209 entries state an etymology in prose that never reaches the Lexemes table. From the first full read of the Dictionary namespace. Of the 212 Ancient Hertic entries, 209 carry a written ===Etymology=== section — 208 of the form "Inherited from Proto-Herta-Olaic {{m|YAP-XX|…}}" and one compound, Dictionary:νουζιφτι — while the remaining three use {{etym-missing}} and are correctly queued. But only one Lexemes row of 526 carries an etym_type: Dictionary:geúrl, the wiki's single Pjany entry, whose headword line reads {{head|YBS-PJ|adjective|gloss=warm|etym_type=inherited|etym_source=YBP-XX}}. Every Ancient Hertic {{head}} leaves both parameters off, so the prose and the queryable record disagree on 209 words. The invariant is the wiki's own: Template:Head documents both fields and says "the Cargo fields power the interlingual queries the Dictionary exists for", and Yezur Wiki:Dictionary structure names this exact query as the payoff — "all words inherited from Proto-A … one query each, self-maintaining" — which today returns one word. Add the two parameters to each of the 209 headword lines, taking both values from the entry's own etymology sentence and inventing nothing: etym_type=inherited + etym_source=YAP-XX for the 208 inherited entries, and etym_type=compound + etym_source=YAQ-HE for Dictionary:νουζιφτι. The values are fully determined by text already on each page, and both are vocabulary Template:Head itself lists. Purely mechanical, but 209 edits, so it wants an explicit go-ahead before a run spends a session on it — and it is the sort of sweep the conventional bot mentioned in Yezur Wiki:Dictionary structure could do instead. pending New 2026-07-25; re-confirmed 2026-07-26 by re-querying the whole table — 526 rows, exactly one carrying etym_type and one carrying etym_source, no drift. One small markup slip to fix in the same pass, if approved: Dictionary:νουζιφτι writes its first element as {{m|YAQ-HE|νουζι}} but its second, φτι, as plain unlinked text, though Dictionary:φτι exists. Not a Cargo issue — just the one inconsistent mention in the whole namespace.
43 2026-07-25 structured data medium Template:Infobox former country, Hertia, Special:CargoTables A Cargo table is declared and written to, but was never created — so one article's structured data goes nowhere. Template:Infobox former country carries #cargo_declare:_table=FormerCountries with fourteen fields and #cargo_stores into it on every use, and it is in use: Hertia fills five of its fields (status, era, region, location, languages) and renders the infobox correctly. But Special:CargoTables lists only five tables — Continents, LanguageFamilies, Languages, Lexemes, Polities — and FormerCountries is not among them; a query against it returns an internal exception rather than an empty result. The comparison that settles it is Template:Infobox polity: also declared, used by no article, and its Polities table nonetheless exists and reports 0 rows. So this is not an empty table, it is an absent one — the declaration was saved but the one-time creation step never ran. One administrative action, then nothing else: from Template:Infobox former country, run Create data (?action=recreatedata). That needs the recreatecargodata right, which an administrator holds and the editing bots do not, so the routine cannot do it. Neither the template nor Hertia needs any change — the row should appear as soon as the table exists. Worth doing before more former countries are written, since every one added meanwhile stores into nothing. pending New 2026-07-25, and confirmed 2026-07-26 that the routine cannot do it: Alompan's own rights were queried directly, and recreatecargodata is false — the account sits in user / autoconfirmed only, holding move, upload and editcontentmodel but neither recreatecargodata nor delete. The comparison that settles absent-vs-empty also still holds: a query on FormerCountries throws MWException while Polities answers cleanly with 0 rows. Third of the three "facts that never reach a table" rows, with #29 and #41.
44 2026-07-25 structural low Category:Auphen errors, Category:Pages flagged for deletion Two maintenance categories are filed as if they were templates. Both end with [[Category:Templates]], whose own page defines it as "Templates used across the Yezur wiki" and which sits under the in-frame root Category:Yezur. Neither holds a template, and neither is one: Category:Auphen errors collects pages whose {{auphen}} call failed, and Category:Pages flagged for deletion collects pages tagged {{delete}}. The second contradicts its own filing in its own wikitext, which carries the comment "Editorial / maintenance category — out of the in-universe frame" — that is the definition of Category:Yezur Wiki ("out-of-frame — about the wiki, not about the world"), not of Category:Templates. As it stands Category:Templates lists three templates and four subcategories, two of the four being these. Reparent both — the same single decision as #24 and #27: either directly under Category:Yezur Wiki, or under a new Category:Tracking categories beneath it, whichever you pick there. Replace the [[Category:Templates]] line on each; nothing else on either page changes, and Category:Auphen errors keeps its __HIDDENCAT__. One line each, mechanical once the parent is chosen. pending New 2026-07-25, re-checked 2026-07-26. Approve this with #24 and #27 as one decision — four maintenance categories, two missing and two misfiled, all waiting on the same choice of container. Both also appear in Special:UnusedCategories this run, which for a tracking category is the good state and not a separate finding. The rest of the tree is sound: every other category has a parent that holds, and no cycles.
45 2026-07-25 factual medium Yezur Wiki:Conventions, Template:Infobox language, Yezur Wiki:Dictionary structure Three project pages still describe the language families as unnamed placeholders. All five families have in-world names and articles — Andusian, Herta-Olaic, Njeshan, Shung-Worrehan, Tacchoan, each with a LanguageFamilies row — but the documentation was never followed through from the rename, and three pages still teach the retired Family A–E scheme as current. (a) Yezur Wiki:Conventions §Naming: "Language families currently carry placeholder labels ("Family A", and so on) until their in-world names are derived; use them sparingly." — flatly no longer true, on the page every other check on this wiki is run against. (b) Template:Infobox language's usage note: "The family value is the plain family page name (e.g. Family A)" — a worked example naming a title that does not exist. (c) Yezur Wiki:Dictionary structure illustrates the Cargo payoff with "all words inherited from Proto-A". Medium severity entirely because of (a). (b) and (c) are mechanical one-word swaps: Family A → Herta-Olaic, Proto-A → Proto-Herta-Olaic (both are what the corresponding real entries use). (a) is your call in one respect: the plain fix is to delete the bullet, since it now only misinforms. If you would rather the section still said something about family titles, the observed practice — and what #28 relies on — is the bare name, so the bullet could instead read "Language families take the bare name (e.g. Herta-Olaic), without language." The routine will not choose between deleting and rewriting a convention; say which. pending New 2026-07-25, re-checked 2026-07-26 with Yezur Wiki:Conventions read in full again — (a) is still live, word for word, in §Naming. If #28 and/or the new #51 are also approved, all three edits fall in the same §Naming list and should be made in one pass. See #46 for the other surviving trace of the same rename — and note that #47 is the same species of defect on the same two project pages: documentation that was never followed through.
46 2026-07-25 open thread low Talk:Family A, Talk:Family B, Talk:Family C, Talk:Family D, Talk:Family E Five talk pages outlived their articles, and hold a thread that has since been settled. Family A through Family E do not exist in any form — no article, no redirect — but all five of their talk pages do. Each carries a single out-of-frame note that the label is temporary and the family's real name is still to be found; Talk:Family A reads "'Family A' is a placeholder label — the family's in-universe name still needs to be derived (its reconstructed ancestor is Proto-A)", and the other four are variants of it. Every one of those names has since been derived, so the notes describe work already finished. The rename evidently recreated the family articles rather than moving them: Talk:Gaillean shows what a genuine move leaves behind — a redirect to Talk:Gaillean language — and none of the five named family articles has a talk page at all. flag-only on the mechanism: the editing bots hold no delete right, so the routine cannot clear them. Two ways, whichever you prefer. (a) Tag each with {{delete}} so they queue in Category:Pages flagged for deletion, which this report lists every run until an administrator actions it — the routine can place the five tags on approval. (b) If any note is still wanted, move it to the named family's talk page first and delete only the remainder. Reading the five, nothing in them survives the rename, so (a) looks sufficient. pending New 2026-07-25 — and one claim in the Issue above is corrected by this run's reading of the deletion log. The family articles were moved, not recreated: Family A through Family E were deleted by Yezur on 2026-07-19, and the log records each one's content as #REDIRECT plus {{delete|Redirect left by the language-family rename}}. So a proper move left a redirect behind, the redirect was tagged and cleared, and it is only the talk pages that were never moved along with their articles. Also confirmed directly this run: Alompan's delete right is false, so (a) tagging remains the only route open to the routine.
47 2026-07-26 structural medium MediaWiki:Sidebar, Yezur Wiki:Main Page, Yezur Wiki:Conventions Two namespaces are documented as part of the wiki's structure and have never held a single page. Meta: — namespace 4, this wiki's project namespace — is named as live out-of-frame space in six places across three pages. Yezur Wiki:Conventions gives it a row of its own in the §Namespaces table ("Meta: — Out-of-frame — Design notes and rationale"), names it in §Where out-of-frame content goes ("It belongs on Talk pages, in the Meta: namespace, or in this Yezur Wiki: namespace"), and names it again in the same section's rule of thumb ("except the Meta:, Talk:, and Yezur Wiki: namespaces"). Yezur Wiki:Main Page lists it first under §Behind the scenes as "about the Yezur project itself; the place for Earth comparisons and design notes" and repeats it under §Conventions. And MediaWiki:Sidebar gives it a permanent navigation slot on every page of the wiki, as Project docs → Special:PrefixIndex/Meta:. But Meta: and Meta talk: hold 0 pages, and list=allrevisions returns nothing for either — no page has ever existed in them, so the sidebar link every reader sees leads to an empty index. The same is true of Help:, which Yezur Wiki:Main Page lists as the third out-of-frame namespace ("how-to guidance for editors") and which Yezur Wiki:Conventions's table omits entirely: also 0 pages, also no revision ever. Everything the two are described as holding is in fact on Talk pages and in the six-page Yezur Wiki: namespace. A decision, then mechanical edits. Say whether Meta: is still wanted as a namespace distinct from Yezur Wiki:. (a) If it is retired — the reading that fits what has actually been built, since every out-of-frame page written so far has gone to Yezur Wiki: or to a Talk page — then drop its row from the §Namespaces table, drop it from the two sentences in §Where out-of-frame content goes and the rule of thumb, drop the §Behind the scenes bullet and the §Conventions mention, and repoint the sidebar's Project docs link at Special:PrefixIndex/Yezur Wiki:, where the six project pages actually are. (b) If it is still wanted, it needs at least one page so the sidebar link is not a dead end, and the two project pages should be made to agree on what belongs there rather than in Yezur Wiki:. Either way the Help: mismatch wants settling in the same pass, since the two project pages disagree about whether it is part of the scheme at all. One caveat on scope: the sidebar sits in the MediaWiki: namespace, which needs the editinterface right — queried directly this run, Alompan does not hold it — so that one line needs an administrator even once approved. The two project pages the routine can do itself. pending New 2026-07-26, from the first full read of the Module, Talk, User, MediaWiki and project namespaces. Same species as #45 — documentation that was never followed through — but load-bearing in a way #45 is not: this is the only navigation link on the wiki that leads somewhere empty, and it is on every page. Recorded as not a finding beside it: Yezur Wiki talk:, Dictionary talk: and Map talk: are empty too, but no page claims otherwise, and a talk namespace fills itself when there is something to discuss.
48 2026-07-26 factual low Module:Auphen/YAQ-HE, Module:Auphen/YBS-PJ Both Auphen data pages open with a header comment their own contents contradict. (a) Module:Auphen/YAQ-HE documents its four keys and describes the last as "sets : named grammar/derivation rulesets (none yet)" — but the sets table immediately below holds 24 of them: the full NOM / ACC / OBL / GEN × SG / PL declensions of noun classes F, M1 and M2, with their own inline commentary on citation forms and rule ordering. (b) Module:Auphen/YBS-PJ says it is "loaded by Module:Auphen/frame via mw.loadData" — but the frame loads it with require, and explains why in a comment of its own: "require (not mw.loadData): loadData's read-only proxy does not enumerate nested tables under pairs() in Lua 5.1, which would hide the categories." The YAQ-HE page's parallel line, "Pure data, loaded by Module:Auphen/frame", is correct; YBS-PJ's is a leftover from before that change. Neither error touches behaviour — both are comments — but each is the first thing an editor reads on the page, and each says the opposite of what the page does. Two one-clause deletions, asserting nothing new. (a) Drop "(none yet)" from the sets line on Module:Auphen/YAQ-HE; if the line should still say something, the accurate form is "named grammar/derivation rulesets (noun declensions F, M1, M2)". (b) Drop "via mw.loadData" from Module:Auphen/YBS-PJ, leaving "loaded by Module:Auphen/frame" to match its sibling. Mechanical. Note that (b) is a page Yezur wrote, so it is a copyedit of your own comment rather than the routine's. pending New 2026-07-26, from reading all nine modules in full for the first time. One thing the same reading turned up that is deliberately not filed as a row, because it bears on dismissed #21 rather than reopening it: that sets table covers classes F, M1 and M2 only. Module:Head declares five noun classes (M1, M2, F, N1, N2) and two verb classes (IS, OO), and the four wanted templates are exactly decl-N1, decl-N2, conj-IS and conj-OO — so building those tables needs new rulesets on this data page as well as the four templates, roughly thirty-two more entries. The to-do note records the templates but not that prerequisite; worth knowing before the task is picked up.
49 2026-07-26 factual low Module talk:Auphen The engine's own behaviour log contradicts itself about %, and the source settles which half is wrong. Module talk:Auphen records divergence D15 as a fixed bug: "% ('same as the target') substitutes on every occurrence in a result, so %% doubles the target (e.g. gemination [C]/%%/_4). The JS replaced only the first %." A few lines below, the Kept behaviours list — the behaviours deliberately not changed — includes "only the first % in a result is substituted". The two statements cannot both be true, and D15 is the one that matches the code: Module:Auphen splits the result on % and joins every part with the target word, under a comment restating D15 almost verbatim. It is not academic — the live Module:Auphen/YBS-PJ ruleset depends on it, [C]/%%/_4 being its gemination rule, which geminates only under D15. Delete the clause "only the first % in a result is substituted;" from the Kept behaviours sentence, leaving the other four kept behaviours exactly as they stand. Mechanical, and it removes a claim rather than adding one. One of those four was checked against the source this run and holds: the empty-ELS case is an explicit early return in the replacement resolver, so an empty else really is a skip and not a deletion. pending New 2026-07-26, from the first full read of the Module namespace and its talk page. The list the stale clause sits in is otherwise accurate, which is exactly why it is worth removing rather than leaving as a curiosity: Module talk:Auphen is the only record of what the engine deliberately does and does not do, and Module:Auphen's own header sends readers there for it ("the full behaviour/divergence log ... live on the talk page"). Distinct from #50, which is the same module's code rather than its documentation.
50 2026-07-26 structural low Module:Auphen An unreachable branch in the affix path, and an else-clause form that is silently dropped along with it. In Engine:handle_affix, the change slot is handled by two branches — one for a change containing #, and one for an empty change carrying only an @-index or span, which is what a pure indexed operation parses to, since the index-stripping helper removes the @n and leaves the change empty. The else slot copies that same two-branch shape, but wraps it in if ELS ~= then — so its second branch tests ELS == inside a block that has already required ELS ~= , and can never run. The same guard also skips the else clause's affix_prep call a few lines earlier. The consequence is not only dead code: an affix rule whose else clause is an @-index alone falls through both guards, the else never applies, and the rule returns the word unchanged with no warning — where the identical form in the change slot works. It is the same class of defect the talk page records as already fixed: D1 reads "the ELS @-index is parsed and used as a fallback instance filter (the JS assigned it to the CHG index, so ELS indices were dead)" — and in the affix path they are still dead. flag-only. This is a change to a live rule engine with an off-wiki test suite behind it, and the routine will not edit module code on the strength of its own reading. The shape of the fix is plain — hoist the ELS ~= guard so the index-only case reaches affix_prep and apply_affix_logic, mirroring the change slot exactly — but it wants a proving test case in that suite first, and the module is Khurouan's. Raised so it is recorded rather than found again later. Worth settling one question before any code moves: whether an index-only else clause on an affix rule is a form the rule notation actually admits. If it is not, the right fix is the opposite one — delete the dead branch and say in a comment why the else slot needs only the # case. pending New 2026-07-26, from the first full read of Module:Auphen — at 38 KB the largest page on the wiki outside this report. The only code defect the sweep found: the UTF-8 codepoint layer, the case tables, the escape layer, the category-explosion guard (opts.explodeCap, default 5,000,000, exactly as the talk page states) and the IPA transposition all check out against their documented behaviour, as do the two data pages' category sets.
51 2026-07-26 naming low Yezur Wiki:Conventions, Category:Countries The worked example for place-qualified category names matches neither the wiki's categories nor the same page's own next paragraph. Yezur Wiki:Conventions gives the form twice as "Polities of Andusia" — in §Categories ("a country in Andusia sits in a 'Polities of Andusia' category that is a child of both 'Andusia' and 'Polities'") and again in §Naming ("Keep narrower place qualifiers, such as 'Polities of Andusia'"). Two paragraphs after the first, the same section writes "Former countries in Andusia". Every place-qualified category that exists uses in, and none uses polities: Category:Cities in Hertia and Category:Ancient cities in Hertia, beside Category:Countries and Category:Former countries. The split runs deeper than the connector. The category side of the wiki says country — Category:Countries, one member, Engil — while the template and Cargo side says polity: Template:Infobox polity declaring and storing into the Polities table. Only Template:Infobox former country and Category:Former countries agree with each other across the divide. Two parts, one mechanical and one a decision. (a) The connector is settled both by practice and by this page's own later sentence: make both worked examples read "in". Mechanical. (b) Whether the house word is country or polity is yours to say — and it is cheap now: Category:Countries holds one page and the Polities table holds none, so nothing has to be moved either way. If country wins, the examples become "Countries in Andusia" and Template:Infobox polity is the odd name out; if polity wins, Category:Countries wants renaming to match, and the routine holds the move right so it could do that on approval. Leaving both words in use is defensible too — but then the examples on the convention page should at least use a form that exists somewhere. pending New 2026-07-26, from re-reading Yezur Wiki:Conventions in full beside all 24 category pages. Third row touching §Naming, with #28 and #45(a) — if more than one is approved, make them in one edit. Recorded as not a finding: neither Category:Andusia nor Category:Polities exists, though the worked example implies both — those are categories not built yet rather than an inconsistency, and the same page asks that new categories be cleared with the operator first. (Named in italics rather than linked, so this report does not itself create two more wanted categories.)
52 2026-07-26 factual low Yezur Wiki:Conventions, Template:On the map The convention set's list of map templates omits the one that articles actually use, and lists four that none do. Yezur Wiki:Conventions §Maps reads, in full: "Link to the Yezur map with {{Node}}, {{Way}}, and {{Relation}} (by object id), or {{Coords}} / {{Coordslink}} (by coordinates)." All five exist, and the transclusion counts show how they are used: {{Node}} by seven articles, and {{Way}}, {{Relation}}, {{Coords}} and {{Coordslink}} by no page at all. Meanwhile Template:On the map is not mentioned, though it is in use on Alompe and is the only one of the six that behaves structurally differently: it renders through MediaWiki's page-status-indicator mechanism, placing a 🌐 On the map link beside the page title rather than inline. Its own documentation carries two rules that are recorded nowhere else — "by convention, put it on the first line of the article", and "If the template appears more than once on a page, the last use wins" — and it states its own scope: points on the map, "not continents or countries, which cannot be reduced to a single point". Add one bullet to §Maps, restating only what Template:On the map's own usage note already says: that a subject resolving to a single point on the map takes {{On the map|lat|lon}} on its first line, which places a title-side indicator rather than an inline link and takes effect once per page; and that continents and countries, which cannot be reduced to a point, do not take it. Nothing new is asserted. Mechanical. The four unused templates are not proposed for removal — a documented template awaiting its first use is not a defect. pending New 2026-07-26, from reading all 25 templates against the convention set. If #28, #45 or #51 are approved this can go into the same edit to Yezur Wiki:Conventions, though it falls in §Maps rather than §Naming. Related but deliberately not flagged: Talk:Alompe records that article's map node id (60111) as an open thread "until a settlement infobox exists to hold it" — a new infobox is a decision the convention set reserves to the operator, so the note is left where it is.
53 2026-07-27 structural medium , Tacchoan The wiki's first image carries an out-of-frame attribution strip, and its colour key cannot distinguish two of the four branches it exists to distinguish. The file was uploaded on 2026-07-27 and placed in Tacchoan §Members; it is a 1283×785 map export, and both defects were read out of the pixels rather than inferred. (a) The attribution strip. A pale bar carrying the mapping software's "© OpenStreetMap contributors" credit is baked into the saved image at its bottom-right corner — rows 778–784 across columns 1159–1283, so the frame's own bottom edge cuts the line of text in half. It renders at full size in the article, where Yezur Wiki:Conventions §Namespaces holds that "everything a reader or editor sees is in-character". It is the most reader-visible break of frame currently on the wiki, and the only one that is not text. (b) The colour key. The caption assigns yellow twice — "yellow for the Kipoa languages, and a small yellow area to denote the Usy language" — and the image bears this out: two separate yellow fields, an eastern strip and a southern island, in the same hue. A reader cannot tell which is which, on a map whose whole purpose is to separate the four branches. Purple (north), green (centre) and the two yellows do match the four bullets' stated geography, and red does sit off to the southwest, away from Taccho. Three parts, and only the third is mechanical. (a) is flag-only: a corrected export is the map's business, not the routine's, and a straight crop of the bottom seven pixels is not a safe substitute — mapped land reaches the bottom edge across the left of the frame (77–108 non-sea pixels in every one of rows 778–784), so cropping would clip the southwestern island chain. There is also a question the routine cannot answer: whether any of the framed data is OpenStreetMap-sourced, in which case the credit is a licence condition and must be re-placed rather than removed. (b) is likewise flag-only — giving Usy its own colour needs a new export. (c) is mechanical and can be done without touching the file: the caption opens on "Red is referring to the Herta-Olaic family" without saying that Herta-Olaic is not a Tacchoan branch at all but the neighbouring family, shown for contrast; one clause fixes that, asserting nothing that Herta-Olaic and Taccho do not already say. pending New 2026-07-27. Verified against the file itself, not the caption: the strip's extent was measured, and the two yellow fields confirmed as the same hue. #54 covers the description page rather than the image. If (c) is approved it can go into the same edit as #55, #56 and the mechanical half of #57, which all touch the same six lines of Tacchoan.
54 2026-07-27 structural medium Yezur Wiki:Conventions, The wiki now holds files, and has no conventions for them. Until 2026-07-27 the site statistics read images 0, and the last report recorded the unused-images check as clean on the grounds that "the wiki holds no files at all". That is no longer true: there is one file, and nothing governs it. Yezur Wiki:Conventions has no §Files — its eleven sections cover voice, namespaces, naming, formatting, categories, infoboxes, open threads, maintenance, maps and sourcing, and say nothing about what a file description page carries, whether files are categorised, or how a source or licence is recorded. The consequences are already visible on the one file that exists: it is the sole entry in Special:UncategorizedImages; no File: namespace category exists for it to join; and its description page is the article caption copied verbatim — the same colour key, word for word, in two places that nothing keeps in step, so approving any caption change (see #53) silently puts them out of sync. flag-only on the substance. What a file description page should carry is a convention decision, and the convention set reserves those to the operator. Three questions settle it: whether files are categorised at all (and if so, whether the category is in-character like every other, per §Naming); whether a source line is recorded, given that these are exports of the map and the question of licence raised in #53; and whether a description page may restate an article caption or should point at it. Once decided the mechanical work is small — one category, one short description — and the routine can carry it out. pending New 2026-07-27, from the first upload in the wiki's history. Deliberately not proposed here: any particular category name, or a licence template. #14 (deferred) is the neighbouring case for pages — uncategorised front pages, where the operator accepted the finding but had no decided approach yet; this is the same shape one namespace over, and may want the same answer.
55 2026-07-27 voice low Tacchoan Four wordings in the new §Members text sit below the encyclopedic register. Yezur Wiki:Conventions §Editorial voice asks for "neutral and third-person, definition-first, like any good reference work". (a) The caption describes the key rather than the subject: "Red is referring to the Herta-Olaic family, while green is the Esselis branch, purple the Rumesselis branch..." — a reference work captions what the map shows, not the act of matching colours to names. (b) "Esselis, the one spoken by the highest amount of population" — amount takes a mass noun, and "the one spoken by" is a conversational stand-in for a plain superlative. (c) "a subfamily that is spoken in the south-east of the continent, as well as spoken on small areas of Lovvocia" — spoken twice in one sentence, and on where the sense is in. (d) "subdivisible into four categories" — category has a working meaning on this wiki, and the same six lines call these things branch or subfamily three times over. Mechanical, and asserts nothing new — every fact stays exactly as written, including which colour marks which branch and which branch sits where. (a) recast as a description: the four Tacchoan branches, named with their colours, and Herta-Olaic identified as the neighbour (see #53(c)). (b) → "the most widely spoken of the four, in the centre of the continent". (c) → "spoken in the south-east of the continent, and in small areas of Lovvocia through colonial ties". (d) → "divided into four branches". pending New 2026-07-27, from reviewing the day's one article edit against the convention set in full. Not flagged in the same passage, and recorded as passing: the lead's "one of the five major Yezuri language families" is the reflexive planet-qualifier already carried by #38, which lists Tacchoan among its pages; the new Kipoa bullet's colonial claim is confirmed by Lovvocia, which independently records Tacchoan languages "in smaller areas — particularly the central region adjoining Vetsia"; and "the continent", used three times unnamed, resolves correctly to Taccho from the first sentence.
56 2026-07-27 factual low Tacchoan Tacchoan calls one of its own branches an isolate, against the wiki's own definition of the word. The fourth bullet reads "Usy, an isolate subfamily spoken on the island of Usings". Category:Language isolates defines the term on this wiki, in full: "Languages with no demonstrated kinship to any language family." Its one member, English language, uses it in exactly that sense — "It is a language isolate: it has no demonstrated kinship with any of the major language families". A branch of Tacchoan has demonstrated kinship by definition: that is what makes it a branch. As written the sentence claims both at once. Mechanical, a two-word swap. "an isolate subfamily" → "the family's only single-language branch", which is what the passage means and what the caption already implies by naming "the Usy language" in the singular. Nothing else in the bullet changes. pending New 2026-07-27. The distinction matters beyond the wording: Category:Language isolates is a live category with a member, so leaving isolate in place invites Usy into it when the article is written, which would put it in two mutually exclusive places at once.
57 2026-07-27 structural medium Tacchoan, Esselis, Rumesselis, Kipoa, Usy, Usings Five subjects were named into existence and none has an article; and the four branches are linked in the caption but left as plain text in the bullets that define them. The 2026-07-27 edit to Tacchoan introduces four branch names — Esselis, Rumesselis, Kipoa, Usy — and one place, the island of Usings. All five are red. They account for the entire rise in wanted pages this run, 31 → 36: four at two incoming links each (the article and the file description page, which repeats the caption) and Usings at one. Separately, the linking is inconsistent within the same six lines: all four branches are linked from the image caption, and all four are plain text in the bullet list immediately below — the bullets being the passage that actually defines each one. Two halves. The mechanical half is the linking: link the four branch names at their bullets, where they are defined. The flag-only half is the articles. Four branch stubs could be written from what Tacchoan already asserts — each branch's position on Taccho, its relation to the others, and Kipoa's colonial reach into Lovvocia — restating wiki-asserted facts only and inventing nothing; Usings cannot, since the article gives it no property beyond being an island where Usy is spoken. Whether those stubs are wanted is the operator's call. pending New 2026-07-27. #11 (deferred) is not this: it covers the empty Cargo member query on this and two sibling articles, which is a language-level gap and stays empty either way, because these five are branches and places rather than languages. Which raises a structural question the routine is not filing as its own row: the branch layer has nowhere to live in the structured data — LanguageFamilies holds the family, Languages holds languages, and neither carries a field for the layer between, so once branch articles exist nothing will relate them to Tacchoan but prose. Adding a field is a schema change and needs the administrative rebuild noted in §Infoboxes and structured data. Talk:Tacchoan does not exist; if the stubs are declined, §Open threads there is where the four names belong. The five names are written unlinked throughout this report, as Template:He-decl and Dictionary:dog were last run: linking them here would add a third incoming link to each and make this page a cause of the very counts it reports.

Dismissed flags

Deferred or rejected findings, kept here so later runs do not re-flag them.

  • #8 (deferred) — Wanted history-period pages Yezuri Age of Exploration / Yezuri Middle Ages. Operator: not canon names for these eras; will not create stubs under temporary names.
  • #11 (deferred) — Andusian / Tacchoan / Shung-Worrehan member-language queries fall back to the default. A content gap, not a data error; operator: no member languages are in yet, add when ready.
  • #12 (rejected) — Greek-letter native names on Hertia / Hertic language / Alompe etc. Operator: fully intentional in-world orthographic style.
  • #14 (deferred) — Uncategorised portal front pages and the root Category:Yezur. Operator: accepted, but no decided approach for handling it yet.
  • #21 (deferred) — The four wanted Ancient Hertic inflection templates (conj-IS, conj-OO, decl-N1, decl-N2). Operator: "will be fixed when the tables are created — already on my to-do." Confirmed present on the to-do list at User talk:Yezur.

Latest run

2026-07-27 (scheduled run) — no operator verdicts were waiting, so nothing in article space was changed; the run was a read-only survey. The quiet broke. After four days in which the only Recent-Changes entries were this report's own, the operator made two edits on 2026-07-27: the first file upload in the wiki's history, , and a substantial expansion of Tacchoan §Members that places it. Site statistics moved accordingly — pages 697 (the new file description page), articles 450 (unchanged), edits 1,295, images 0 → 1, job queue 0.

Fixes applied: none — all thirty-one rows still read pending, and this page's last six revisions are Alompan's own.

Dismissed: none.

New findings: five, all arising from the day's two edits. The image was examined as an image — downloaded and read at the pixel — rather than taken on the caption's word, which is what turned up #53.

  • #53 (medium) — the new map carries the mapping software's "© OpenStreetMap contributors" credit baked into the saved file, bottom-right, where the frame's own edge cuts the line of text in half. It renders at full size in Tacchoan: the most reader-visible break of frame on the wiki, and the only one that is not text. The same row records that the colour key assigns yellow twice, to Kipoa and to Usy — confirmed in the file as two separate fields in the same hue — so the map cannot distinguish two of the four branches it exists to distinguish.
  • #54 (medium) — the wiki now holds files and has no conventions for them. Yezur Wiki:Conventions has no §Files; the one file is the sole entry in Special:UncategorizedImages with no File: category to join; and its description page is the article caption copied word for word, so the two will drift the moment either changes.
  • #55 (low) — four wordings in the new §Members text sit below the encyclopedic register, among them a caption that describes the act of matching colours to names rather than what the map shows, and "subdivisible into four categories" where the same passage says branch or subfamily three times over.
  • #56 (low) — Tacchoan calls Usy "an isolate subfamily", against this wiki's own definition at Category:Language isolates — "no demonstrated kinship to any language family" — which a branch of Tacchoan contradicts by definition.
  • #57 (medium) — five subjects were named into existence with no article behind them: the branches Esselis, Rumesselis, Kipoa and Usy, and the island of Usings. All four branches are linked from the image caption and left as plain text in the bullets that define them.

The wanted-pages prediction held exactly. Last run removed a redlink this report had created by itself and predicted the count would fall 32 → 31, with wanted templates staying at 4 and wanted categories at 46. Templates and categories came in at 4 and 46 as predicted, and the five new redlinks in #57 account for the whole of the rise to 36 — four at two incoming links each, Usings at one, 31 + 5. Template:He-decl is gone from the list, confirming the self-inflation fix took.

Clean this run: linter errors 0; broken redirects 0; double redirects 0; Category:Auphen errors 0; the deletion queue 0; and unused images 0 — a check that now means something, since the wiki's one file is in use on Tacchoan. The orphaned-pages reading that last run reported as an unexplained drop, 110 → 106 with no intervening edit, came in at 106 again and has held; dead-end pages held at 109. Both remain entirely Dictionary: pages.

Verified consistent — the new material against existing canon. The new Kipoa bullet's colonial claim is independently confirmed by Lovvocia, which records Tacchoan languages "in smaller areas — particularly the central region adjoining Vetsia"; the article's three unnamed uses of "the continent" resolve correctly to Taccho from its first sentence, and Taccho returns the reference ("the sole major Yezuri language family native to Taccho"); the infobox's reach=Colonial (limited) is the weakest of the five families' reach values, which is what a single colonial foothold in Lovvocia should give; and the map's four coloured fields match the four bullets' stated geography — purple north, green centre, yellow south-east — with red lying off to the south-west, away from Taccho, consistent with its being the neighbouring family rather than a Tacchoan branch.

Structured data this run — unchanged and in sync: Continents 8, Languages 7, LanguageFamilies 5 (the Tacchoan row matches its infobox field for field), Lexemes 526, Polities 0. The Tacchoan member query still falls back to its default, which is #11 (deferred), not a new finding: the four names added this run are branches, not languages, and would not populate it.

Pending tally: the table holds 36 rows — #26 (high); #23, #28, #29, #31, #32, #36, #38, #42, #43, #45, #47, #53, #54, #57 (medium); #24, #25, #27, #30, #33, #34, #35, #37, #39, #40, #41, #44, #46, #48, #49, #50, #51, #52, #55, #56 (low); and #22 (resolved, awaiting only a verdict to clear) — plus 5 findings in Dismissed flags. No row has been resolved by an operator verdict since 2026-07-19, eight runs ago. Twelve rows are purely mechanical and need only a one-word verdict — #23, #28, #33, #34, #39, #42 (mechanical but large), #44, #48, #49, #52, #55, #56 — and four more carry a mechanical half: the second half of #41, the first half of #51, part (c) of #53, and the first half of #57. #55, #56, #53(c) and the first half of #57 all touch the same six lines of Tacchoan and can be carried out in a single edit.

Retrieved from "https://yezur.xyz/w/index.php?title=Yezur_Wiki:Daily_routine/Report&oldid=1318"