Summary

  • APNIC's September 2025 Executive Council minutes said a liaison to the APNIC Foundation Board had existed since 2016 while its scope and responsibilities remained undefined. The same record set two safeguards: avoid fiduciary conflict and support, rather than replace, three existing governance interfaces.
  • In May 2026, the EC adopted an EC Foundation Liaison role and separately authorised the EC Chair and Director General to agree a protocol with APNIC Foundation covering observer attendance, confidentiality and information sharing. The separation between role and protocol is sensible.
  • The reviewed public sources do not identify the protocol's present state, effective date, review point or supersession line. That does not show that the protocol is absent or the liaison inactive. APNIC could publish a narrow status receipt while keeping protected content private.

A repaired role is the starting point

The strongest reading of APNIC's record is not that something went wrong. It is that the institution noticed an old ambiguity and acted on it.

The minutes of the Executive Council meeting of 7-8 September 2025 say an EC Liaison to the APNIC Foundation Board had been appointed in 2016, but the role's scope and responsibilities remained undefined. That is unusually candid governance language. It separates the fact that a role exists from the harder question of what the role may do.

The same minutes did not jump from diagnosis to an unlimited mandate. They supplied two constraints. A liaison arrangement should complement APNIC's position as the sole member of APNIC Foundation without creating fiduciary conflicts. It should also support three structured interfaces—strategic oversight, strategic alignment and operational alignment—without replacing them. The EC then agreed to update the role and to engage the Foundation about involving the liaison with its Board.

That sequence matters. A liaison is useful precisely because two institutions need information to cross a boundary. It becomes dangerous when the crossing is mistaken for authority over either side. APNIC's 2025 formulation recognised both conditions at once.

Adoption did not finish the operating design

The minutes of 13-14 May 2026 record the next state. The EC considered a proposed role description and related governance arrangements intended to improve communication and alignment while preserving governance interfaces and confidentiality. Resolution 2026-05-02 then adopted the EC Foundation Liaison role as presented.

But the resolution did something else, in a separate clause. It authorised the EC Chair and Director General to agree with APNIC Foundation on a protocol for the role. Three subjects were named: observer attendance, confidentiality and information sharing arrangements. The resolution passed unanimously.

This is a coherent division of labour. The EC decides that the role should exist and fixes its governance purpose. The people responsible for making the interface work agree the detailed protocol with the other institution. A board need not negotiate every meeting invitation or information category in public session.

The distinction nevertheless creates a small state machine. “Role adopted” is not the same as “protocol agreed”. “Protocol agreed” is not necessarily the same as “effective”. “Effective” does not identify the incumbent, the meetings covered or the review date. And a protocol that later changes should not silently overwrite the version under which earlier exchanges occurred.

The public minutes establish the first state. They authorise the route towards the second. In the source set reviewed for this article, they do not identify where the protocol sits now.

A liaison is not an extra director

The boundary is easier to understand by beginning with APNIC Foundation's design. APNIC's 2016 explanation of the Foundation's structure described APNIC as the Foundation's single member and assigned corporate governance and fundraising functions to the Foundation Board. The current public Board page presents the directors who hold that institutional function.

A liaison inhabits neither role. The liaison is not the sole member acting through a new channel, and is not made a director merely by observing. The liaison can carry context, explain APNIC priorities, listen to Foundation deliberation within the agreed boundary, and return information to the proper APNIC interface. None of those actions should replace a board resolution, management decision or member power.

That is why the phrase “observer attendance” is consequential. Standing attendance, attendance by invitation and attendance only for specified agenda items create different access surfaces. An observer might receive papers for an entire meeting or only for the item they attend. They might speak, answer questions or simply listen. They do not acquire a vote merely because they enter the room.

A usable protocol should say which class applies. A public receipt need not reproduce invitations or papers. It can state the class and the authority that set it.

Confidentiality is part of the control, not an excuse to omit the state

APNIC's resolution expressly includes confidentiality. That is not a warning sign. It is a necessary element of a serious interface.

Foundation directors may handle donor terms, grant assessments, personnel matters, risk reports, legal advice and negotiations. APNIC may hold member, operational or security information that should not travel merely because two institutions are related. A liaison needs a rule for what can be received, what can be carried back, what must remain within the originating body and how conflicts are handled.

Publishing all of that material would defeat the control. Publishing none of the protocol's state is not the only alternative.

A registry can say that a protocol is effective without disclosing a protected annex. It can identify that attendance is invitation-based without naming confidential agenda items. It can identify the permitted direction of information by category—APNIC to Foundation, Foundation to APNIC, or both—without revealing the information itself. It can say who owns the protocol and when it will be reviewed.

The point is not radical transparency. It is a distinction between the existence and state of a governance instrument, which can usually be public, and the protected content administered under it, which often should not be.

What the current public surfaces establish

The APNIC Executive Council page explains the EC's composition, budget role, fee authority, standing committees and contact routes. The Foundation's Board page explains who serves as directors. Neither frozen page used the literal liaison or observer terms when captured for this review.

That observation is narrow. Websites have different purposes. A role may sit in an induction pack, a board portal, a governance register not indexed by a search engine, or a document that was updated after the captured copy. The protocol may have been agreed and may already be used well. The current liaison may be entirely clear to both institutions.

The evidence therefore supports a documentary finding only. The public chronology runs from an acknowledged undefined role, through an agreed redesign, to an adopted role and authority to negotiate its protocol. It does not supply a public state for the resulting protocol in the reviewed sources.

Search silence is not institutional absence. It is, however, a reason to publish a durable pointer when the governing resolution has already told readers that a separate instrument matters.

The minimum protocol-state receipt

The receipt can be short enough to sit beside the resolution. It should begin with the role name and version, the authority that adopted it and the resolution identifier. It should identify the protocol state using a controlled vocabulary: draft, agreed, effective, suspended, retired or superseded.

An effective date and next review date would distinguish a live instrument from an intention. The observer-attendance field could say standing, invited or agenda-limited. A confidentiality field could identify the rule class and the authority responsible for it, without exposing protected information.

Information sharing should be recorded as directions and categories. For example, the receipt could say that strategic-planning context may move both ways, while privileged advice and personal data remain with the originating body. It need not list a single document.

The receipt should also restate the 2025 boundary: the liaison supports strategic oversight, strategic alignment and operational alignment but does not replace them. A conflict or recusal field should identify which institutional process takes over when the liaison cannot participate. Finally, owners, review date and supersession lineage should preserve the life of the protocol.

This is not a new governance layer. It is an index to the layer APNIC has already created.

Why members have a legitimate interest

APNIC and APNIC Foundation are distinct institutions with a close structural relationship. Foundation work concerns Internet development, training, community support, research and grants across the same region in which APNIC's members operate. Communication between them can reduce duplicated effort and align capability investment with observed needs.

Members do not need access to confidential Foundation deliberation to understand that interface. They do have a reasonable interest in whether the role adopted by their EC has moved into an operating state, which boundaries constrain it, and how APNIC will know when it needs review.

That interest is not a claim that every liaison exchange changes registry policy. The May resolution is explicit that the role is about communication and alignment, and the 2025 record says it should not replace established interfaces. The value of a receipt is precisely to stop ordinary communication from being mistaken for delegated decision power.

The evidence stops before performance

The five first-party sources establish a historical structure, an acknowledged ambiguity, a redesign and a formal adoption. They do not show attendance logs, board packs, an executed protocol, an incumbent's current status, an information flow, a conflict, a complaint or an outcome.

The article therefore cannot judge performance. It cannot say that the role is inactive, that a protocol was withheld, or that confidentiality was breached. It cannot infer a fiduciary problem merely because the 2025 minutes named that risk as something to avoid.

The question is smaller and answerable. When one resolution adopts a role and authorises a separate protocol, what public evidence marks the transition from authority to operation? At present, the reviewed record gives the authorisation. A protocol-state receipt would give the transition.