Summary

  • Resolution 2026-23 records unanimous written consent on 14 September 2026, adds Luis Martinez and Hendrik Ike to the Nominations Committee, adds Frederic Taes and David McAuley to the Elections Committee, and approves the 2026–2027 Elections Timetable “as attached”. The four appointments are not candidate nominations, and the resolution date is not a nomination-opening date.
  • At the research cutoff, the resolution was public but its paragraph did not expose an attachment link; the public 2026 election page still described the previous cycle, and the committee pages still showed the initial July rosters. Those are bounded observations about public retrievability, not findings that the attachment does not exist, the appointments are ineffective or publication is late.
  • A calendar-activation receipt should join the Board act to the timetable version and hash, durable URL, complete committee roles, conflicts and recusals, exact UTC nodes, responsible notification actors, system state, certification, challenges and corrections. This is an editorial proposal, not an existing Internet Society rule.

One resolution, two kinds of authority

Resolution 2026-23 is short enough to tempt a short reading. Adopted unanimously by written consent on 14 September 2026, it says the Board adds Luis Martinez and Hendrik Ike to the 2026–2027 Nominations Committee, adds Frederic Taes and David McAuley to the Elections Committee, and approves the 2026–2027 Elections Timetable as attached.

The sentence does two different jobs. The appointments complete the personnel who will administer important parts of the selection process. The timetable authorizes the sequence in which constituencies, candidates, ballots and challenges will move. Both are corporate acts, but neither tells a reader by itself whether a form is open, a notice has gone out, a voting credential has been issued or a deadline has passed.

That distinction protects the record from two easy errors. The four people named in the resolution were appointed to committees; they were not nominated as trustee candidates. And 14 September is the date of Board approval, not automatically the opening date for candidate nominations. The operative opening date belongs to the approved timetable and to the public actions that implement it.

Meeting 196 supplies the earlier half of the committee record. On 25–26 July, the Board appointed Ramanou Biaou as Nominations Committee chair and Sharon Kent as a member. It appointed Caleb Ogundele as Elections Committee chair, with Victor Kuarsingh, Charles Mok and Brian Trammell as members; President and CEO Sally Wentworth serves ex officio. The minutes said additional members would be appointed later.

Read together, the July minutes and September resolution evidence a four-person Nominations Committee—Biaou, Kent, Martinez and Ike—and an Elections Committee consisting of Ogundele, Kuarsingh, Mok, Trammell, Taes and McAuley, with Wentworth ex officio. This is a reconstruction from two Board records. It should not be confused with a claim that every public landing page had already caught up.

What the public record did and did not show

At the research cutoff on 21 September, the written-consent page exposed the text of Resolution 2026-23. Its wording said the timetable was attached, but the resolution paragraph presented no attachment link in a cache-bypassed retrieval. The public WordPress media endpoint for that page returned no child media. A prospective /elections/2027/ path returned a 404, while the established /elections/2026/ page continued to show the 2025–2026 cycle and its exact dates. The Nominations and Elections Committee pages continued to display the initial July rosters.

None of those observations establishes that the Board lacked an attachment, that no timetable exists, that the September appointments are ineffective or that Internet Society missed a deadline. A document can exist within a Board packet before it is exposed through a page. A page can move to another URL. A content system can lag a valid resolution. Public-source research must report the access state it actually sees without converting a retrieval gap into a legal conclusion.

The narrower conclusion is still important: a reader could verify the corporate act, but could not yet reproduce the exact approved calendar from the same public evidence path. The resolution tells the public that a clock was approved. It does not, in the observed rendering, disclose the versioned clock face.

The procedures turn dates into operating duties

Internet Society’s Procedures for Selecting Trustees show why the exact calendar matters. They say the Board makes annual election details public on the election website and that publicly posted election information—including the call for nominations, timetable, candidate biographies and statements, and petition records—must be retained in perpetuity.

The procedures allocate work to identifiable actors. The chief financial officer certifies eligible organizational-member and chapter lists against a cutoff date in the timetable. Organizational members are asked to name Election Representatives; chapters identify Voting Delegates. At the start of the cycle, the Nominations Committee publishes the call, eligibility criteria, forms and deadlines, and notifies the community.

They also create minimum intervals. Nominations remain open at least 30 days. Initial slates and notifications appear at least 30 days before the election. A petition period lasts at least 14 days, with a threshold of seven percent of the relevant eligible constituency, rounded up. The final slate is published at least ten days before election day. Electronic voting lasts at least 14 days, and Internet Society sends a receipt for each vote.

After voting, the Elections Committee certifies results to the Board within five days and announces them within five days of certification. A challenge may be filed with the President within seven days of the announcement. Following consultation with the committee chairs and Board, the President communicates the Board’s final decision within seven days after the challenge period.

These rules are not the missing dates. They are constraints, owners and intervals into which the approved timetable must fit. The procedures’ “typical” months are guidance, not permission to invent exact 2026–2027 deadlines. Only the approved timetable can supply those nodes.

Committee composition is a safeguard, not the whole control system

The committee charters provide another layer of verifiability. The Nominations Committee has three to seven individual members. At least two must be people who are not officers, trustees, employees or contractors of Internet Society, and no committee member may be elected or selected as a trustee in the year of service. Its work includes setting nomination procedures and criteria, soliciting candidates, naming slates, handling petitions and liaising with the IAB. It has no Board powers.

The Elections Committee has a trustee or emeritus-trustee chair, the President ex officio and at least two additional individual members. Its members also may not become trustees during the year they serve. It proposes the timetable for Board approval, establishes ballots, monitors and counts the vote, certifies results, administers challenges and announces outcomes. It too has no Board powers.

Those structural safeguards answer who may perform a function and what the function is. They do not by themselves reveal a member’s conflicts in a particular cycle, whether a recusal occurred, which person sent a notice or which system state opened at a given time. Nor does a name establish a person’s viewpoint, constituency or independence. An auditable cycle needs role and action records, not speculation about biographies.

A calendar-activation receipt

The missing public object can be small. A calendar-activation receipt would not replace the timetable or create another committee. It would join the legal, documentary and operational states that already exist.

It should include:

  1. Resolution 2026-23, its 14 September approval date and the mode of unanimous written consent.
  2. The approved attachment’s title, version, checksum, durable URL and publication timestamp.
  3. Complete Nominations and Elections Committee rosters, each person’s role, term and the source of appointment.
  4. Applicable conflict-of-interest policy, disclosed conflicts, recusals and substitute decision-makers, with privacy limits where needed.
  5. Every operative date and time in UTC, plus any displayed local-time conversion and the rule for resolving discrepancies.
  6. The actor responsible for each call, eligibility notice, credential, system opening, reminder, ballot distribution and result notice.
  7. A publication and notification log showing when the page changed and which constituencies were notified.
  8. State markers for nominations, eligibility certification, petitions, final slates, voting, certification, announcements and challenges.
  9. Links between any correction and the superseded version, preserving both the reason and history.
  10. The final Board record establishing closure after certification and any challenge.

This proposal is Daniel Kade’s editorial recommendation, not a current Internet Society requirement. It need not publish ballots, private candidate data or confidential conflict details. A hash can prove which timetable was approved without exposing a Board packet; a recusal entry can identify the affected matter without narrating private circumstances. The aim is minimum sufficient provenance.

Precedent without a deadline

The previous cycle shows that this model is practical. In September 2025, Meeting 190 and the associated resolution record combined additional committee appointments with approval of the 2025–2026 timetable. The later public election page displayed exact dates for calls, petitions, voting, results and challenges.

That history demonstrates a documentary pattern: Board approval can become a detailed public operating calendar. It does not prove when the 2026–2027 page must appear, and it does not justify calling the current state late. Its value is simpler. The institution already knows how to expose the clock. The activation receipt would make the transition from resolution to running process explicit and versioned.

Evidence limits

The public sources reviewed here do not establish whether the attachment was circulated privately, whether a different public URL was being prepared, when notices would be issued, or whether any committee member has a cycle-specific conflict. They do not show any nomination, petition, vote, certification or challenge for the new cycle. They also do not support a judgment about any named person’s views or representative status.

They do establish the resolution, its approval method and date, the four additions, the earlier appointments, the committees’ formal duties, the process minimums and the public-retention duty. That is enough to identify an activation boundary without alleging procedural failure.

Sources