Summary

  • APNIC’s corporate-document index offers one entry for the APNIC Definition Document. Its destination presents APNIC-080 version 004, dated 20 April 2026, with the status DRAFT.
  • APNIC’s stable text endpoint presents the same document reference as version 003, dated 20 July 2023, with the status Active. Both versions say they implement prop-145 and obsolete version 002.
  • APNIC’s active editorial policy supplies the rule that resolves the conflict: where HTML and text differ in content, the text version is the official document. Yet the current definition page links version 004 and version 002, not the still-active version 003.
  • A two-state document manifest—active version, draft version, hashes, diff, review status, activation event and supersession chain—would preserve legitimate drafting while making authority visible at the point of use.

Two identity tables, one document number

The first surprise is not hidden in legal prose. It sits in the identity table at the top of APNIC’s definition page. The table says APNIC-080, Version 004, 20 April 2026, DRAFT. It says the document implements prop-145 and obsoletes version 002. The version number links to a five-page PDF carrying the same identity.

The second identity table is at APNIC’s stable text address, definition-document.txt. There, APNIC-080 is version 003, dated 20 July 2023, and its status is Active. It too says that it implements prop-145 and obsoletes version 002.

This is not necessarily a contradiction in institutional intent. A document can have an active edition and a later proposed edition at the same time. Indeed, version 004 is plainly labelled as a draft. The problem is the join between those states. APNIC’s corporate-document index describes its collection as corporate documents and official guidelines, gives the APNIC Definition Document a single entry, and sends the reader to the page whose body is the draft. On that page, the visible version links are 004 and the obsoleted 002. The captured page does not link version 003 or the stable active text.

A reader who arrives through the normal hierarchy therefore sees a draft and an old predecessor. The current official version exists, but it is not in the local chain.

The strongest defence is APNIC’s own hierarchy

There is a disciplined reading of this arrangement, and it should come before criticism.

APNIC-112, the active document editorial policy, defines the editorial process for official documents. It says the Secretariat releases a public draft and opens a one-month comment period, considers comments, and publishes the final version as an official document after the review steps are complete. Drafts are not anomalies in that system; they are part of the system.

The same policy also decides what happens when formats diverge. Official documents will normally be published in text and HTML. Hyperlinks, formatting and graphics may differ, but if content differs, the text version is considered official. PDF is permitted where layout requires it. On that rule, the stable text marked Active is the defensible authority, while the HTML and linked PDF marked DRAFT are a later state under development.

That is a stronger position than an unlabelled overwrite. The status is visible. The active file is still available. The authority rule is public. A specialist who already knows all three locations can reconstruct the intended order without guessing which date is newer.

The 2026 context also offers a sensible reason for a new draft. APNIC members passed two by-law reform resolutions on 12 February. The second included administrative renumbering and consistency changes. APNIC’s current by-laws page shows version 004 as a draft and says it was amended by the member resolution. A definition document that cross-references by-law numbers would need to move with that package.

Drafting, then, is not the deficiency. Coordinated drafting may be exactly the responsible action.

The versions do not merely wear different labels

The content shows why authority cannot be left implicit. Version 003 defines the “Dispute Resolution Document” as sections 73 to 81 of the APNIC By-laws. Version 004 points instead to by-laws 81 to 89. The later draft also changes the defined label Company to The Company. These may be entirely appropriate alignment edits, but they produce different answers to a reader following a cross-reference.

The identity metadata contains another divergence. Version 003 records the date of original publication as 1 December 2001; version 004 records 1 December 2003. This Article does not decide which historical year is correct. It treats the discrepancy as a useful demonstration: version control is about the identity table as well as the clauses below it.

Both versions also say they obsolete version 002. That makes sense for version 003, which became active in 2023. On the draft version 004 page, however, the same predecessor label does not tell the reader whether 004 is a proposed successor to 003, a parallel revision branched from 002, or metadata carried forward from an earlier working file. Again, none of those possibilities proves a faulty internal process. It proves that the public chain does not explain itself.

Prop-145 makes the interface unusually important

Prop-145 was called “Single Source for Definitions”. Its stated objective was to make one definition document the place where terms are used and interpreted consistently across APNIC policy documents. The Secretariat’s impact assessment described APNIC-080 as the definitive source of definitions, subject to necessary variations in individual documents. The proposal page now records the status as Implemented.

The history is concrete. The proposal reached consensus in September 2022, completed final comments in October, and was endorsed by the Executive Council on 17 November. APNIC opened an editorial comment process in June 2023. That notice included a redline for APNIC-080 and requested comments by 17 July. The proposal history places the end of the editorial period on 20 July 2023, the same date carried by active version 003, and says the policy was published as APNIC-127 version 013.

None of this means prop-145 forbids a later definition draft. A single source can still have versions. The lesson is almost the reverse: once one document becomes a dependency for many other documents, the state of that source must be easier to read, not harder. “Single source” should mean a single navigable authority chain, not a requirement that every format display the same work-in-progress text.

What the current page asks a reader to know

To identify the active definition today, a reader must perform four steps that the page does not narrate:

  1. notice that the main document body is labelled DRAFT even though it sits under the ordinary corporate-document entry;
  2. know that APNIC maintains stable text files at a separate FTP hostname;
  3. find the active version 003 there, despite the current page linking only versions 004 and 002; and
  4. locate APNIC-112 and apply its text-over-HTML rule.

That is recoverable evidence, but it is needlessly specialist evidence. It also makes citations fragile. One analyst can quote the current HTML definition that points to by-laws 81–89. Another can cite the official text pointing to sections 73–81. Both can honestly say they used APNIC-080. Only a version and status in the citation reveals why the answers differ.

The operational cost is modest but real. Policy editors can copy the wrong cross-reference. Agreement reviewers can treat a future definition as current or an active definition as stale. Search engines can privilege the richly rendered draft over the plain-text authority. Archives can record the page without recording the file that governed at capture time. None of those outcomes is proven here; they are the predictable failure modes of an unjoined version surface.

A small manifest is enough

APNIC does not need to hide the draft, duplicate every page or publish confidential legal advice. It needs to display the state transition next to the document identity.

A useful manifest would name the active version and the current draft separately. For each it would provide the date, status, content hash and stable URL. It would show the exact predecessor and proposed supersession chain; explain that the draft aligns with the 2026 by-law package if that is its basis; link the public comment notice and disposition where one exists; provide a readable diff; and identify the event that makes the draft active, including an effective date. Corrections would append a new entry rather than silently rewriting the old one.

The control is intentionally smaller than a new policy process. APNIC-112 already supplies the process. The manifest would expose its result at the point where readers choose a version.

What this record does not establish

The public evidence does not establish that version 004 is legally operative. It does not establish that the 2026 by-law amendments are ineffective. It does not prove that APNIC omitted a required consultation, lacks an internal version register, or has no commencement condition, legal filing or unpublished review record. It does not show a member relying on the wrong definition or suffering harm.

Nor is the DRAFT label itself evidence of concealment. It is evidence of disclosure. The narrower finding is that APNIC discloses the draft state on the page but does not disclose the active state beside it, even though the active state remains retrievable and APNIC’s own process says why it controls.

The distinction matters. Institutional transparency is not achieved by eliminating working documents. It is achieved when a reader can see the line between work in progress and operative text without possessing the institution’s filing conventions in advance.

Sources