Summary

  • At the online AFRINIC Board meeting that opened at 09:08 UTC on 20 January 2021, the Technical Committee appeared as agenda item 4.4. The minutes said it had been inactive for months, had completed the work for which it was constituted and had a scope more operational than Board-related. Resolution 202101.594 dissolved it unanimously.
  • The strongest reading is benign: an idle advisory layer can obscure ownership, duplicate management work and persist after its purpose has expired. The public record nevertheless does not show the charter, accepted outputs, unresolved items, successor owners, retained escalation route, record custodian or later assurance arrangement.
  • A proportionate answer is not committee permanence. It is a versioned closure receipt that joins mandate to accepted deliverables, distinguishes completed work from open or abandoned work, assigns every continuing control and risk, preserves records and gives the Board a route to obtain assurance without micromanaging operations.

L3 — The committee that ended in one paragraph

The online meeting began at 09:08 UTC on 20 January 2021. Quorum was confirmed. Among a sequence of committee reports, the Technical Committee came before AFRINIC's Board as item 4.4. The treatment recorded in the minutes was strikingly compact. The committee had been inactive for the past months. It had completed the work for which it had originally been constituted. The Board considered its scope more operational than Board-related and agreed that it should be dissolved. Benjamin Eshun proposed the resolution, Adewale Adedokun seconded it, and Resolution 202101.594 passed unanimously.

Those facts support a clear legal-corporate end state. The committee ceased to exist by a unanimous act of the Board. They also support the reasons that the Board itself chose to record: inactivity, completion of the original work and a judgement that the remaining subject matter belonged more naturally in operations. They do not, by themselves, display the control transfer that ought to sit between the second proposition and the third. A committee can finish a finite assignment while matters around that assignment continue.

An operational function can move to management while the evidence needed to understand earlier decisions remains in an archive. A Board can stop reviewing day-to-day work while retaining a duty, within the ordinary corporate sense, to know whether important controls are owned and working.

That is the narrow issue raised by this resolution. It is not whether the Technical Committee deserved eternal life. It is whether mandate completion, acceptance, residual risk, operational ownership, escalation, record custody and future assurance remained legible after the committee disappeared.

The official sequence gives the decision some context, but not a complete answer. In August 2019, Resolution 201908.512 reconstituted the Technical Committee with Christian D. Bope, Adedokun E. Adewale, Robert F. Nkusi and the Chief Executive Officer. In December, Resolution 201912.541 expressly included a five-person Technical Committee among the Board Standing Committees: Christian Bope, Vika Mpisane, Subramanian Moonesamy, Serge Ilunga and the Chief Executive Officer.

In September 2020, Resolution 202009.570 again reconstituted Board Standing Committees and named Oluwaseun Ojedeji, Benjamin Eshun and the Chief Executive Officer for the Technical Committee. Then, four months later, the January 2021 minutes reported inactivity, completion and an operational rather than Board-related scope before recording dissolution.

The changing rosters prove only what the resolutions say: the Board constituted or reconstituted the committee with those named participants at those times. They do not license a story about faction, allegiance, competence, conflict or performance. The presence of the Chief Executive Officer on each listed version does not reveal the committee's detailed remit or the way advice and execution were separated. Nor does the word “Technical” tell us which systems, services, projects, vendors, incidents, architecture choices, reports or security controls, if any, came before it. A name is an identifier, not a charter.

The January minutes add one relevant procedural fact. An earlier action requiring Board committees to review their Terms of Reference within two weeks was marked closed and completed. That indicates that a general review action had reached a recorded end. It does not append the Technical Committee's original or revised Terms of Reference, say what changed, or connect a particular version of that document to the dissolution. “Closed” is a status. It is not automatically a documentary bridge from mandate to accepted output and onward ownership.

The limits of the accessible record therefore matter as much as its affirmative statements. The official minutes and Board registers establish the meeting, the agenda, the sequence of reconstitutions, the Board's reasons, the proposer and seconder, the unanimous vote and the dissolution. In the public material assembled for this analysis, however, the original charter and reviewed Terms of Reference are not exposed.

Neither are a work programme, an index of completed deliverables, the committee's technical reports, acceptance criteria, Board sign-off against those criteria, a register of open risks, an operational handoff, a record-custody plan, a retained escalation route or a post-dissolution assurance arrangement.

This is an evidence boundary, not an accusation. A document absent from the accessible record may have existed privately. AFRINIC may have held working papers, confidential annexes, management assignments or archives that were not published. The Board's completion statement may have rested on material not attached to the minutes. Nothing in Resolution 202101.594 proves that records were lost, work was unfinished or operations were left ownerless. Equally, a reader cannot reconstruct those safeguards from the published decision alone.

The correct conclusion is not that no handoff occurred, but that the public account does not demonstrate one.

That distinction prevents a routine corporate sunset from being inflated into a scandal. The Board had a strong, practical case for closure. A committee that has finished a finite mandate and then remains inactive can become a redundant layer. If its remaining subject is operational, continued Board-committee involvement may blur the line between oversight and execution. Staff may wait for advice that is no longer needed; the Board may be drawn towards detail better handled by management; and duplicated review may make responsibility harder, rather than easier, to locate.

Dissolution can prevent an advisory body from becoming permanent through inertia. It can return authority for day-to-day corporate action to the people expected to exercise it.

On that reading, Resolution 202101.594 was not the removal of a necessary safeguard but the simplification of AFRINIC's internal architecture. The committee had done what it was created to do. Its practical subject had migrated to operations. The clean response was to close it, not to preserve an empty box on an organisation chart. A replacement committee would not necessarily have improved anything.

The benign case should be accepted in full because it sharpens, rather than weakens, the accountability question. If the committee's work was complete, what counted as completion? If the remainder belonged to operations, which role received each continuing responsibility? If the committee no longer needed to exist, who kept the records required to explain or revisit its work? If management now owned execution, where could a significant technical disagreement or unresolved risk be escalated? If the Board stepped away from operational detail, what later assurance would let it distinguish healthy delegation from simple loss of visibility?

These questions do not presume a particular technical remit. They define the junctions that any clean closure should make visible. A finite mandate needs an identifiable version and a sunset condition. Claimed outputs need an inventory and acceptance against stated criteria. Remaining work needs a status that distinguishes open, deferred and deliberately abandoned items. Continuing operations need named owners with actual implementation authority. Residual risks need custodians and review dates. Records need durable custody. Escalation needs a route. Board assurance needs a cadence proportionate to the importance of the transferred controls.

The committee itself is not the prize. Reproducibility is. Months or years later, a new director, executive, auditor or technical lead should be able to answer a simple chain of questions without relying on the memory of the people in the 2021 meeting: what was this body asked to do, what did it produce, who accepted the work, what remained, where did continuing responsibility go, where are the records, and how can a material problem return to the right level of attention?

Resolution 202101.594 answers the first-order corporate question—did the committee end?—and gives a concise reason. It leaves the second-order operational answer outside the published frame. That is not proof of failure. It is the case for a closure receipt.