Summary

  • The May 2026 status report lists eleven topics under one heading, "Items In Progress and Under Drafting," and gives each an explicit state: In progress, Drafting or No change.
  • All nine topics from the Q1 2026 report reappear in May. One label changed from "Recognition (Unanimity minus one)" to "Recognition Threshold," and one combined topic split into three.
  • In the versions inspected on 12 November 2026, no entry is assigned to a named registry and no entry carries a calendar due date. The record shows movement; it does not set a delivery test.

A form that records every field except the two that bind

Open the May 2026 report and the structure is consistent to the point of being bureaucratic. Each topic carries a title, a Background section, a Feedback section, sometimes a Response, an explicit Status, an action or decision statement, and a pointer to a Relevant Section of the governance document. Across eight pages the entries sit together under a single combined heading rather than being separated into work in progress and work under drafting.

The states themselves are plain: "In progress," "Drafting," "No change." There is no ambiguity about vocabulary and no invented scoring. A reader can see, topic by topic, whether text is being argued, written, or left alone.

The gaps appear one level down. No entry assigns its commitment to a specifically named registry. The report refers to "RIRs," to "other RIRs," to the "affected RIR," and names the NRO Number Council and ICANN as actors — but the five registries do not appear as individual owners of individual paragraphs. Nor does any entry carry an item-level calendar date. Dates in the report are contextual; timing is expressed in relative terms, for example the next version.

The most concrete action language in the document, changing regular-audit frequency to once every five years and adding definitions in the next version, still arrives without a named registry or a deadline.

That is not a drafting error. It is a design choice with a cost, and the cost is exactly the thing a counterparty wants from a status report.

Nine in February, eleven in May

The Q1 2026 report runs to six pages and uses the same field structure, sorted differently: 4 entries In progress, 4 Drafting, 1 No change, nine topics in all. The In progress list reads Recognition Review, Recognition (Unanimity minus one), Derecognition and Ad Hoc Audit Thresholds, and Emergency Continuity. The Drafting list reads Document Structure, Transition and Continuity, Audit Obligations, and Derecognition (Rehabilitation as a part of derecognition). One entry, Derecognition (Audit as a part of derecognition), sits at No change. The report also says of itself that it opens no new consultation or comment period.

Set the two documents side by side and the motion is real. All nine February subjects reappear in May. The recognition topic loses its parenthetical and becomes Recognition Threshold. The combined Derecognition and Ad Hoc Audit Thresholds entry separates into Derecognition Threshold, Audits, and Ad Hoc Audit, and the last of those is renamed Compliance Review.

Two readings compete here, and the record does not choose between them for us. The first is administrative: a drafting process that has reorganised its own agenda, split an overloaded heading into three workable ones, and renamed a topic to match what it now contains. That is what work looks like from the inside. The second is less flattering: relabelling and subdivision raise the apparent granularity of a report without demonstrating that any contested sentence was decided. Nine topics became eleven. Nothing in either document tells a reader which of those eleven moved from argument to agreed text.

The distinction matters because of what a status report is for. A document that says "Drafting" is honest and, by itself, useful: it describes the state of the drafting. A document that says "Drafting" while naming no author and no date is honest too, but it cannot be late. Nothing in the format can ever fail. Each successive report can only report more motion, in the same three labels, against the same subjects — and there is no baseline against which a reader can say this cycle was worse than the last.

Where caution ends and the question begins

This desk's reading is bounded by what it could actually obtain. Two attempts on 12 November 2026 to reach the process and adopting instrument behind the series — the Number Council decision and the consultation page — failed: a provider 503 with an unknown outcome, then a 968-byte snapshot whose only content was that the NRO governance pages could not be browsed to confirm a resolution or a reporting mandate. No adopting decision, no stated reporting cadence, no named resolver of open items and no version-2 draft text across rounds was obtained.

None of that is evidence that such an instrument or obligation is absent; it is the boundary of this route, and every statement above about what the reports do not carry is scoped to the two versions inspected.

With that boundary in place, the defect claim has to be conditional, and it is worth stating exactly why. If the Number Council's own decision or process rules place ownership and cadence somewhere else, then these ledgers are a summary view of a firmer instrument and the absence of owners inside them is a formatting observation. If no such instrument assigns those things, then the series is the accountability locus — and it holds no name and no date. The difference between those two worlds is a single document this review did not reach.

What survives either way is the falsifiable part. Recurrence across reporting periods, relabelling, and the splitting of one topic into three are all observable in the record, and none of them is a completed decision. A reader who wants to know whether the governance document is advancing has to supply the missing test themselves, because the format will not.

That is the practical legacy of a well-organised ledger. It makes the process visible and the liability invisible, and it leaves each resource holder, board member or regulator holding the same question: show me the entry with a registry's name on it and a date beside it, and I will believe the paragraph is being delivered.