Editorial Notices

An editorial notice is how this wiki says out loud that one of its own pages needs work. Three of the content policies name a notice as their enforcement, and none of them describes what the notices are. There are two kinds, and they behave differently: an editor places one on a single article, and the site derives the other from every page at once.^[1]

Notices an editor places

A notice is a block, added to a page the same way a paragraph is, and it renders as a bordered strip above the prose. Six variants exist, each with fixed wording an editor can override with a sentence about the specific page.

Read again on 28 September 2026, the whole wiki carries three of them across 380 pages, all the advertisement notice: on Blue Chick NFTs, UniSci and UniX. From at least 19 August it carried five, the other two being the stub notice on Kernel layer and Application layer; on 21 September the edits that expanded both pages removed those notices and said so in their revision messages, as the procedure below asks. All three advertisement notices sit on projects the Ecosystem directory records as dormant or closed, which is where promotional copy is most likely to be left over from a livelier period. The other three variants have never been used, so an editor reaching for one is setting the precedent rather than following it.

The notice nobody places

May be outdated is the one variant the site can raise on its own. A page whose facts were last checked more than 180 days ago gets the notice inserted above its first block, worded with the date of the last check or with the fact that no check is recorded. It is a rendering rather than a stored block, so it disappears the moment the page is re-verified, and it stands aside when an editor has already placed an outdated notice by hand.

An editor records a check by stamping the page, which the maintenance sweep does with scripts/mark-verified.mjs. That stamp is the only thing that resets the clock: editing a page also moves it, because an unstamped page falls back to the date of its last edit. 312 of the 378 pages under a category carry an explicit verification stamp, read at 23:05 UTC on 24 September 2026, and at that reading none of them was past the threshold. Age is counted in whole days and the notice needs more than 180 of them, so the oldest page on the wiki, last touched at 15:56 UTC on 28 March and 180 days old at that reading, raises the notice by itself from 15:56 UTC on 25 September 2026 unless someone acts first.

Which page that is complicates the rule. The two oldest by last check are XRD Domains at 180 days and Radix Namespace at 87, and both sit in LOCKED_PAGES – the two-entry list the wiki’s write path refuses to edit, and which a maintenance script is required to check for itself. The first outdated notice this wiki raises will therefore land on an article the sweep cannot rewrite. Clearing it by stamping would still work, because mark-verified.mjs writes the date and never consults the lock, and it would assert a check the editor had no power to act on had anything turned out to be wrong. Where the notice fires on a locked page, leave it standing and refer the article to whoever holds the lock.

Tracking categories

A notice sits on the page it describes, where only a reader of that page sees it. The Maintenance index inverts that: it runs four predicates over every page and publishes the pages that fail as work queues. Nobody files a page into a queue and nobody removes it. Fix the page and it leaves the list on the next revalidation.

• Orphaned – no other page links here, so a reader can only arrive by search or by the category index. 11 pages on 20 September 2026, still the largest queue and down from 13 on 4 September.
• Unsourced – the page carries no external link at all, which the verifiability standard treats as a page that cites nothing. 16 pages, unchanged in count since 4 September. The predicate counts a page’s external links by matching href=" against its stored blocks, and a references block holds its citations in a url field, so a page whose sources all sit in its reference list reads as citing nothing. Seven of the sixteen are that case, carrying sixty reference URLs between them, and this page is one of the seven. Of the nine that carry no link of any kind, four are category hub articles and two are pages the site generates from its own data, which leaves three ecosystem articles that cite nothing: Arcane Labyrinth, EtherealDAO and XRD Domains.
• Missing required metadata – a field the page’s tag path declares as required is empty, so its infobox and its category facets are incomplete. 3 pages, up from two: AI Agents & x402 Payments and Radix Context for AI Agents, both missing Status, and the Ecosystem hub article, which inherits the Status and Category required of every project page in the directory and is not a project.
• Outdated – the same 180-day predicate that raises the synthetic notice. Empty, and an empty queue is not rendered, so the heading is absent from the index rather than showing a zero.

The queues and the notice variants share two names and no machinery. Unsourced as a queue is computed from the absence of any outbound link; Needs citations as a notice is a judgement an editor makes about a claim that has one. A page can sit in the queue without carrying the notice, and the reverse holds too.

Clearing a notice

A notice is an address to the next editor, so removing it is an editorial act with a record. Fix what the notice describes, delete the block in the same edit, and say in the revision message what changed – every page’s revision history is public, and a notice that vanishes without an explanation reads as a page that was tidied rather than corrected. Removing a notice while the problem stands is the one move the policy rules out.

The reverse also applies. Adding a notice, rather than rewriting a page on the spot, is the right move when the fix needs a source or a judgement the current editor cannot supply, and neutral point of view asks for exactly that on a promotional page.

Separate from all of this, every page carries an optional quality grade on a six-step scale from Stub to Featured. It is assessment rather than a work queue, it is set by hand, and it is set on eight pages, seven of them the policy pages themselves. A stub notice and a Stub grade can disagree, and neither reads the other.

See also

• Maintenance – the live tracking categories
• Verifiability
• Neutral point of view
• No original research
• Notability
• Freshness
• Conflict of interest