Summary

  • APNIC's 13–14 May 2026 EC minutes say the Council adopted a “Shepherd” model for key topics, with individual EC members appointed to lead discussions on allocated areas.
  • The same minutes later ask the Secretariat to prepare a proposed list of key topics and categories for EC consideration. They do not publish a final list, identify any Shepherd or define the role.
  • Five frozen current APNIC governance pages contain no literal shepherd reference. That is a snapshot of those pages, not proof that no internal assignment or unpublished note exists.
  • A public topic-assignment register and one common role note could separate briefing, sponsorship and communication from recommendations, express delegation and collective EC decisions without exposing confidential papers.

Boards rarely fail for lack of nouns. They fail when a new noun is asked to carry authority that nobody has described.

APNIC's minutes for 13 and 14 May 2026 introduce one such noun with unusual economy. Under the Chair's update, the EC discusses how individual members might assume greater responsibility for particular subject areas to strengthen accountability and transparency in community engagement. It then agrees to a “Shepherd” model for key topics, under which EC members would be appointed to lead discussions on allocated areas.

Near the end of the meeting, the Council returns to the subject. The Secretariat is asked to prepare a proposed list of key topics and categories for EC consideration, including possible groupings. That sequence matters. The model was adopted; the taxonomy was still to be proposed. The public minutes checked here do not show the resulting list, any appointment or a common mandate.

This is not evidence of a hidden chain of command. It is the more ordinary condition of a governance change arriving in minutes before it arrives in the public architecture around the board.

The strongest case for a shepherd

The model deserves a defence before it receives a specification.

APNIC's EC must follow registry services, policy development, finance, risk, security, community participation, legal obligations and relationships with other Internet institutions. The elected members do not become full-time staff merely because the agenda is long. If every subject has to be reconstructed by the whole Council at every meeting, scarce board time is spent reloading context rather than applying judgment.

A topic Shepherd can reduce that tax. One member can follow the papers between meetings, ask the Secretariat for a briefing, remember why a question was deferred and ensure that a difficult subject returns to the agenda. Community members may find it easier to understand who is listening, even when the answer must still come from the Council. The full EC may make a better decision because one colleague has done the work of keeping the issue coherent.

Confidentiality also limits what should be visible. APNIC's current roles and obligations page sets out confidentiality expectations for EC members. Legal advice, security detail, Member information, personnel matters and early deliberation do not become public merely because a member follows a topic. A useful mandate can be public while the material handled under it remains protected.

The problem, then, is not individual attention. It is role identity.

What the current pages tell a Member

The current Executive Council page describes a familiar structure: seven elected members and the Director General, with a Chair, Treasurer and Secretary elected from the seven. The current roster attaches those formal roles to named people and identifies the Director General as ex-officio. It does not label any person as a topic Shepherd.

The same EC page publishes a second model of divided work. APNIC has two standing subcommittees: the Finance, Risk and Audit Committee and the Remuneration Committee. Their membership is listed, and each has an adopted charter. The FRAC charter and the Remuneration Committee charter state purpose, authority, objectives, composition, appointment, duties, meetings, reporting and conduct controls.

Both charters draw the same bright line. The committee may make recommendations, but it cannot make a decision in the EC's name or on its behalf unless the EC has expressly delegated that power. That clause is not proof that a Shepherd needs a six-page charter. It is proof that APNIC already has a plain institutional grammar for saying what delegated work can and cannot become.

The current By-laws reinforce the grammar. EC members serve in their personal capacity and in the interests of the APNIC membership, not their employing Member organisation. Decisions of the EC are made by majority vote of those present, subject to the stated higher threshold for removing the Director General. Chair, Treasurer and Secretary have specified duties. Subcommittees may receive lawfully delegatable powers and duties conferred by the EC.

The transparency page then gives readers routes into minutes, corporate documents and other institutional records. Across that page, the EC page, roster, roles page and By-laws as frozen for this article, a case-insensitive literal search found no instance of shepherd.

That negative finding must stay in its box. It does not establish that APNIC has no internal topic list, that appointments have been made secretly or that no other page mentions the model. It establishes something narrower and still useful: the five current public surfaces a reader would naturally consult did not explain the new role when captured.

Six ordinary questions expose the boundary

Imagine a Secretariat team preparing a difficult paper. Which EC member should receive an early briefing? May that member ask for additional work? Can the member promise that an issue will be put on the agenda? May the member describe the Council's position to an external audience? What happens if the topic intersects the member's employment? When is the assignment reviewed or handed over?

None of those questions accuses a Shepherd of overreach. They are the questions that make a coordination mechanism usable.

The answers may be modest. A Shepherd might be allowed to request information through a named Secretariat counterpart but not direct staff. The role might sponsor an agenda item but not guarantee its adoption. It might explain the state of a discussion while making clear that the EC has not decided. A conflict might send the topic to another member or to the Chair. A short note to the full EC might close each cycle.

Without a common role note, each topic can develop its own unwritten answer. The risk is not necessarily misconduct. It is variance. One Shepherd becomes a diligent reader, another an informal spokesperson, another a gate through which a subject must pass. Outsiders cannot tell whether those differences are designed, tolerated or simply accidental.

That ambiguity can burden the Shepherd too. A named member may be treated as personally responsible for a collective outcome, or be pressed to disclose a position that the Council has not taken. A clear boundary is not merely a restraint. It is protection against authority being projected onto a person who does not possess it.

Publish the assignment, not the boardroom

The missing artifact can be small. APNIC could publish one topic-assignment register and one common role note.

The register would name the topic, the Shepherd, the appointment date, a review date and the state of the assignment. The role note would explain purpose, the information that may be requested, the path by which an item can be sponsored for an agenda, the boundary for external communication, the difference between a personal view and an EC position, the limits on recommendations and decisions, the conflict and recusal path, the record returned to the full Council, the Secretariat counterpart and the handover or closure process.

No confidential paper belongs in that register. No legal advice, Member file, security finding or personnel discussion needs to be published. Even the subject label can be generalized where specificity would reveal a protected matter. The public object describes the container, not everything placed inside it.

Versioning matters. Topics will be combined, divided or retired. EC membership changes. A public register should therefore retain effective dates and a short supersession history rather than silently replacing one assignment with another. The point is not to count activity. It is to preserve the identity of the role over time.

A coordination role should return to the collective

The most important line in the design is the return path.

The minutes say Shepherds will lead discussions. “Lead” can mean convene, prepare, explore, frame or advocate. Those verbs have different consequences. The By-laws, however, make collective decision authority visible. The role note should connect the two: a Shepherd may prepare and sponsor work, but a recommendation is identified as such, an express delegation is recorded as such, and an EC decision remains a decision of the Council.

That distinction improves accountability without turning every conversation into a resolution. It lets a topic mature. It gives staff and community members a human point of contact. It preserves the full EC's ability to disagree with the person who has followed the subject most closely.

Good board design does not eliminate informal work. It makes informal work legible enough that nobody mistakes it for the final act.

APNIC's May decision may become a useful piece of institutional plumbing. The public record is one fitting short. A topic list tells readers what the Council is following. A common mandate tells them what following means. Together, those two small objects would let the Shepherd model increase accountability without quietly changing the location of authority.