Yezur Wiki:Daily routine: Difference between revisions

Revision as of 12:29, 16 July 2026

Task list for the automated daily maintenance routine, carried out by the Alompan account. Each run does two things, in order: first it carries out the verdicts the operator has left in the /Report table, then it surveys the wiki and files new findings there. The survey itself changes nothing; the only canon edits in a run are fixes the operator has explicitly marked approved or amended. When unsure whether something qualifies as a finding, leave it out or file it flag-only — a short, trustworthy report beats a noisy one.

On each run

1 · Carry out the operator's verdicts

Read the flagged-items table on /Report and handle every row whose Status is not pending:

approved — carry out the Suggested fix as written, as ordinary encyclopedia edits with in-character summaries. Remove the row.
amended — carry out the fix described in the Notes cell (the notes override the suggested fix). Remove the row.
deferred / rejected — remove the row and add one line to Dismissed flags on /Report: id, verdict, a one-sentence summary, and any operator note. Dismissed findings are not re-flagged by later runs.
A row that cannot be carried out as instructed — the fix fails, or turns out to need a judgment call after all — stays in the table: set its Status back to pending and explain why in Notes.

A row whose fix is flag-only has nothing mechanical to apply: it is resolved either by an amended fix in Notes, or by dismissing it.

2 · Survey

Structural health — from the API (list=querypage): wanted categories (priority — propose creating each with a best-guess parent and a one-line description; flag-only if the parent is unclear); wanted pages and templates; orphaned and uncategorised pages; double and broken redirects. Propose the concrete fix where it is unambiguous.
Structured data — for each table in Special:CargoTables: rows missing a key field, duplicate values that should be unique, and references to pages that do not exist. Propose a fix only where it is mechanical.
Markup — linter errors (list=linterrors): name the page and propose the fix.
Recent changes — for articles changed since the last run (see the scan-state comment at the bottom of /Report): factual contradictions against linked or related canon; voice breaks (real-world references, out-of-frame intrusions, non-encyclopedic register — see Yezur Wiki:Conventions); and open threads (placeholders, dangling references) to propose as Talk-page notes.

3 · File and summarise

New findings become new rows in the flagged-items table with Status pending, dated with the run. Skip anything already in the table or on the Dismissed-flags list — match on substance, not wording. Ids are never reused; continue from the highest id ever issued (check both the table and the dismissed list).
Rewrite the Latest run section of /Report: the date; fixes applied (with revision ids); flags dismissed; new flags filed; the clean checks; and a tally of what is now pending.
Update the scan-state comment at the bottom of /Report.

Statuses

Status	Set by	Meaning	On the next run
`pending`	Alompan	awaiting the operator's review	stays in the table
`approved`	the operator	the suggested fix is wanted, as written	fix applied, row removed
`amended`	the operator	a different fix is wanted — described in Notes	Notes applied, row removed
`deferred`	the operator	real, but not worth acting on now	moved to Dismissed flags
`rejected`	the operator	not an issue	moved to Dismissed flags

Nothing is ever applied without an explicit approved or amended. Findings that need a genuine editorial or creative decision are filed flag-only and left to the operator.

@@ Line 1: / Line 1: @@
-Task list for the automated daily maintenance routine, carried out by the [[User:Alompan|Alompan]] account. The routine is '''report-first''': each run surveys the wiki and posts a numbered report to [[/Report]], and changes no article content on its own. A human reviews the report, approves items, and the approved fixes are applied on a separate, human-triggered run.
+Task list for the automated daily maintenance routine, carried out by the [[User:Alompan|Alompan]] account. Each run does two things, '''in order''': first it '''carries out the verdicts''' the operator has left in the [[/Report]] table, then it '''surveys the wiki''' and files new findings there. The survey itself changes nothing; the only canon edits in a run are fixes the operator has explicitly marked <code>approved</code> or <code>amended</code>. When unsure whether something qualifies as a finding, leave it out or file it flag-only — a short, trustworthy report beats a noisy one.
 == On each run ==
-Acting as Alompan, work through the checks below, then overwrite [[/Report]] with the findings. '''Change no canon during a run''' — the only page written is [[/Report]]. When unsure whether something qualifies, leave it out or mark it flag-only; a short, trustworthy report beats a noisy one.
+=== 1 · Carry out the operator's verdicts ===
-=== 1. Structural health ===
+Read the flagged-items table on [[/Report]] and handle every row whose Status is not <code>pending</code>:
-From the API (<code>list=querypage</code>):
-* '''Wanted categories''' (priority) — used but not created. Propose creating each with a best-guess parent and a one-line description; flag-only if the parent is unclear.
-* '''Wanted pages''' and '''templates''', '''orphaned pages''', '''uncategorised pages''', '''double''' and '''broken redirects''' — list them, and propose the concrete fix where it is unambiguous.
-=== 2. Structured-data consistency ===
+* <code>approved</code> — carry out the '''Suggested fix''' as written, as ordinary encyclopedia edits with in-character summaries. Remove the row.
-For each table in [[Special:CargoTables]]: rows missing a key field, duplicate values that should be unique, and references to pages that do not exist. Flag; propose a fix only where it is mechanical.
+* <code>amended</code> — carry out the fix described in the '''Notes''' cell (the notes override the suggested fix). Remove the row.
+* <code>deferred</code> / <code>rejected</code> — remove the row and add one line to ''Dismissed flags'' on [[/Report]]: id, verdict, a one-sentence summary, and any operator note. Dismissed findings are '''not re-flagged''' by later runs.
+* A row that cannot be carried out as instructed — the fix fails, or turns out to need a judgment call after all — stays in the table: set its Status back to <code>pending</code> and explain why in Notes.
-=== 3. Markup ===
+A row whose fix is ''flag-only'' has nothing mechanical to apply: it is resolved either by an <code>amended</code> fix in Notes, or by dismissing it.
-Linter errors (<code>list=linterrors</code>) — name the page and propose the fix.
-=== 4. Recent changes ===
+=== 2 · Survey ===
-For articles changed since the last run: factual '''contradictions''' against linked or related canon; '''voice''' breaks (real-world references, out-of-frame intrusions, non-encyclopedic register — see [[Yezur Wiki:Conventions]]); and '''open threads''' (placeholders, dangling references) to propose as Talk-page notes.
-== The report ==
+* '''Structural health''' — from the API (<code>list=querypage</code>): '''wanted categories''' (priority — propose creating each with a best-guess parent and a one-line description; flag-only if the parent is unclear); '''wanted pages''' and '''templates'''; '''orphaned''' and '''uncategorised''' pages; '''double''' and '''broken redirects'''. Propose the concrete fix where it is unambiguous.
+* '''Structured data''' — for each table in [[Special:CargoTables]]: rows missing a key field, duplicate values that should be unique, and references to pages that do not exist. Propose a fix only where it is mechanical.
+* '''Markup''' — linter errors (<code>list=linterrors</code>): name the page and propose the fix.
+* '''Recent changes''' — for articles changed since the last run (see the scan-state comment at the bottom of [[/Report]]): factual '''contradictions''' against linked or related canon; '''voice''' breaks (real-world references, out-of-frame intrusions, non-encyclopedic register — see [[Yezur Wiki:Conventions]]); and '''open threads''' (placeholders, dangling references) to propose as Talk-page notes.
-Overwrite [[/Report]] with a dated, numbered list, most severe first. Format each item as:
+=== 3 · File and summarise ===
-: '''N.''' <code>[category · severity]</code> <page(s)> — the issue in a sentence. '''Fix:''' the concrete edit, or ''flag-only''. '''Status:''' pending
-Close with a tally, e.g. "18 items — 3 high, 9 medium, 6 low".
+* New findings become new rows in the flagged-items table with Status <code>pending</code>, dated with the run. '''Skip''' anything already in the table or on the Dismissed-flags list — match on substance, not wording. Ids are never reused; continue from the highest id ever issued (check both the table and the dismissed list).
+* Rewrite the '''Latest run''' section of [[/Report]]: the date; fixes applied (with revision ids); flags dismissed; new flags filed; the clean checks; and a tally of what is now pending.
+* Update the scan-state comment at the bottom of [[/Report]].
-== Approving and applying ==
+== Statuses ==
-A human reviews [[/Report]] and changes the <code>Status:</code> of each wanted item from <code>pending</code> to <code>approved</code> (leaving the rest). On a separate, human-triggered apply run, Alompan performs '''only''' the <code>approved</code> items — as ordinary encyclopedia edits, with in-character summaries — and sets each to <code>applied</code> with its revision id. Nothing is ever applied without an explicit <code>approved</code>. Items that need a genuine editorial or creative decision stay flag-only and are left for a human.
+{| class="wikitable"
+! Status !! Set by !! Meaning !! On the next run
+|-
+| <code>pending</code> || Alompan || awaiting the operator's review || stays in the table
+|-
+| <code>approved</code> || the operator || the suggested fix is wanted, as written || fix applied, row removed
+|-
+| <code>amended</code> || the operator || a different fix is wanted — described in Notes || Notes applied, row removed
+|-
+| <code>deferred</code> || the operator || real, but not worth acting on now || moved to Dismissed flags
+|-
+| <code>rejected</code> || the operator || not an issue || moved to Dismissed flags
+|}
+Nothing is ever applied without an explicit <code>approved</code> or <code>amended</code>. Findings that need a genuine editorial or creative decision are filed flag-only and left to the operator.
 [[Category:Yezur Wiki]]