Summary

  • Resolution 201410.208 did not commission a future drafting exercise. It approved a Policy Manual that had already been collated, after recording the Board’s view that the instrument was a consolidated policy document and that due process had produced it.
  • The resolution proves a Board act of adoption. It does not disclose the manual’s full identity, version, contents, source-policy inventory, authority hierarchy, owner, effective date, implementation record, change history or supersession record.
  • Consolidation can be excellent corporate housekeeping: it can reduce contradictory instructions, map responsibilities and give staff one controlled reference. Yet without a visible authority map, collation can also become an unreviewable point at which delegation, amendment and exception rules appear to move.
  • AFRINIC’s control of an internal manual is real private governance, bounded by the authority already supplied to the company and its actors. Approval of that manual created no sovereign, legislative, regulatory, licensing, policing, punitive, confiscatory, arbitral or judicial power.

A three-part act, not a drafting order

Resolution 201410.208 is compact enough to invite careless paraphrase. Its structure is nevertheless important. The Board regarded the Policy Manual as a “consolidated policy document”; it recognised that “due process” had been followed to arrive at the document; and it approved the Policy Manual “as collated.” Those are three distinct propositions, each stated in the past or completed form. The instrument was before the Board as an assembled document. The operative act was approval. The resolution did not direct somebody to begin drafting a manual later.

That distinction is not grammatical trivia. A direction to draft would establish the beginning of a process and might prompt questions about the mandate given to the drafter, the consultation expected and the authority reserved for final adoption. Approval of an already collated document sits at a later stage. It tells us that some process had occurred and that the Board accepted its product. It therefore raises a different set of questions: What texts were gathered? Were their meanings preserved? Which actor had authorised each source rule? Was the work merely editorial, or did it include substantive changes? Which version did the Board see?

What did approval cause to happen next?

The public entry answers none of those questions. It gives no exact day in October 2014, no full title, no version number, no link or attachment, and no table of contents. It does not name an author, collator, custodian, policy owner, authorised editor, implementing office or review body. It records no vote count, quorum, individual vote, effective date, circulation step, staff acknowledgement, training, compliance check, later amendment or supersession. Its value lies in proving a limited institutional act: the Board approved the unnamed instrument as collated.

The phrase “due process” must be handled with the same precision. It shows what the Board recognised. It does not, by itself, identify the steps followed, the people involved, the notice given, the comparisons performed, the objections considered or the reasons accepted. Nor does the label “consolidated policy document” prove that every component rule was copied faithfully or placed at the correct level of authority. Institutional descriptions are evidence of an institution’s recorded position; they are not substitutes for the underlying record needed to test the position.

Within roughly a paragraph, then, the central conflict becomes visible. Consolidation can make authority traceable by gathering scattered decisions, delegations and procedures into one controlled reference. But an unnamed, lower-order manual can also become the point where limits, delegations, waivers and exceptions are silently relocated, even if nobody intended such a result. The published entry proves adoption by the Board. It does not prove the instrument’s contents, commencement, implementation or legal effect.

The useful promise of a single manual

There is a strong practical reason for organisations to consolidate internal policies. Work becomes unreliable when staff must reconstruct current instructions from years of minutes, memoranda, circulars, approvals and local practice. Search costs rise. Different teams may hold different copies. A later instruction may qualify an earlier one without marking it obsolete. New employees may learn an informal shortcut rather than the authorised procedure. Auditors may see an outcome but struggle to determine which rule governed the decision when it was made.

A controlled manual can solve much of this. It can place the applicable instruction beside its owner, approval route and escalation path. It can show where a manager has discretion and where the matter must return to the Board. It can distinguish a mandatory control from guidance. It can collect exception procedures in one place instead of leaving them in personal inboxes. If a provision changes, a single version history can tell users what changed, when and under whose authority. The result is not merely convenience. It can improve consistency, responsibility and institutional memory.

For a private technical coordinator, those gains have operational value. Members and network operators depend on predictable administration, even though the coordinator does not possess public-law jurisdiction over them or over the Internet. A staff member who can identify the source and limit of an instruction is less likely to turn a routine administrative choice into an assertion of general power. An accountable owner can resolve conflicts. A clear escalation route can keep discretionary exceptions from becoming unwritten policy. A review date can prevent a temporary instruction from surviving indefinitely through inertia.

The words “as collated” are compatible with this benign purpose. They may describe careful housekeeping: already valid texts gathered without substantive alteration, checked against their sources, organised for use and approved in a stable form. The Board may have been satisfied that an appropriate internal process had occurred. Sensitive details may properly have remained inside the organisation. A public resolution register is not expected to reproduce personnel files, security instructions, legal advice or every operational annex.

But the same efficiency that makes consolidation useful creates a governance obligation. Once users turn to one manual instead of many source documents, the manual becomes the practical interface to authority. Its reliability depends on whether it preserves the source, scope and rank of every instruction it organises. The manual cannot become more authoritative merely because it is easier to read. Its value comes from accurately carrying forward authority that exists elsewhere, not from converting editorial coherence into a new source of power.

That is why identity and versioning are not cosmetic details. If the approved document cannot be stably identified, later readers cannot know whether the copy before them is the copy the Board approved. If its components are not mapped to their sources, users cannot tell whether a provision reflects a member decision, a Board decision, an express delegation or a routine operational procedure. If its hierarchy is unstated, a neatly written sentence may appear equal to a constitutional rule even though it is not. Consolidation succeeds only when it simplifies access without flattening authority.

The narrow finding

The public record supports neither celebration nor accusation. It does not show that the collation changed authority, and it does not show that it preserved authority. It does not prove a defective process, an unlawful clause, a hidden delegation, a dispute, a victim, a loss or personal misconduct. Equally, the Board’s compressed wording does not close the questions that a dependable consolidation should close.

The defensible finding is narrower. Resolution 201410.208 turned an already collated but publicly unidentified document into a Board-approved internal reference point. The entry records corporate adoption, while leaving the instrument’s version, source map, hierarchy and change controls outside the published record. That is an auditability gap. It is not proof of abuse.