Summary

  • Resolution 201211.160 declared that AFRINIC's 2012 bylaws would take effect on 1 January 2013, making a detailed private-company control map the organisation's stated operating constitution.
  • The text organised three membership classes, member powers, nomination and election machinery, meetings, voting and proxy rules, funding and fees, a nine-seat Board, an advisory Council of Elders and the procedures through which the company would act.
  • Article 13.4 did not force an instant Board replacement: alternate directors were to leave as their terms expired from 2013, with full correspondence to the new structure expected by 2015; draft 2013 AGMM minutes record members voting to maintain that transition.
  • AFRINIC's public chronology remains unresolved. A later timeline says the Board adopted the bylaws on 8 October 2012; a 25 October notice still planned final review and ratification for 20–25 November; a dated preface says final approval occurred on 8 January 2013; and the Board page labels the resolution “Ratified in Feb13.”
  • The missing public bridge does not by itself prove invalidity, fraud, backdating or unlawful retroactivity. It does mean the record does not disclose the decisive vote, member authorisation, legal opinion, filing, comment-disposition matrix or complete transition ledger needed to trace the asserted commencement from consultation to authority.

Midnight, with paperwork on both sides

At midnight on 1 January 2013, an institutional clock crossed a line that AFRINIC had drawn for itself. Resolution 201211.160 said that the organisation's new bylaws would take effect that day. On AFRINIC's account, its Board had reviewed comments from the community and a final version submitted by the Review Working Group. The resolution thanked the Bylaws Review Working Group, legal counsel Me Ashok Radhakisoon and community participants for their work and support. The result was meant to be more than another draft: it was the declared start of a new operating constitution.

The change mattered because constitutions allocate control before anyone needs to test it. The 2012 text said who could belong to AFRINIC, which members could vote, how directors would be nominated and elected, how meetings would be summoned, how unresolved election questions would be handled, how fees could be reviewed or waived, how the Board would be structured, and how company decisions and records would be authenticated. For a member-facing registry, those are not decorative provisions. Operators depend on continuity, accurate records and predictable institutional action.

A change to the organisation's internal control map can therefore affect real planning even though it is not public legislation.

Yet the start line is clearer than the route to it. AFRINIC's surviving materials place important procedural markers on both sides of 1 January. A later institutional timeline says the Board adopted the bylaws on 8 October 2012 and published them on 15 October. A contemporaneous announcement dated 25 October instead described another draft and scheduled comments through 9 November, working-group review from 12 to 19 November, and final Board review and ratification for 20–25 November. A preface carrying the date 8 January 2013 says the Board approved the final text that day while also saying it took effect one week earlier.

The Board page places Resolution 201211.160 under February and labels it “Ratified in Feb13.”

This is not a semantic puzzle with a safely assumed answer. “Adopted,” “approved,” “ratified,” “published” and “effective” may describe distinct corporate steps, later authentication, minute approval or imprecise retrospective summaries. The sources do not explain which. Nor does the resolution number establish a November act merely because of how its digits appear. The responsible question is narrower: what control system did AFRINIC declare operative, what transition made that system practicable, and what public evidence is still needed to connect consultation and legal work to the act of adoption?

A constitution for a company, not for a continent

The first boundary is on the face of the instrument. The bylaws define the Company as AFRINIC Ltd, incorporated in Mauritius. Article 3.1 describes it as a private company limited by guarantee. That form does not make its rules inconsequential. A private-company constitution can allocate voting rights, impose procedures on company organs, organise contractual relationships and determine how internal authority is exercised under applicable law. Its effects may be commercially and operationally serious.

But corporate consequence and public sovereignty are different kinds of power. AFRINIC's service region, technical role and importance to network operators do not convert its members into a continental electorate or its community process into a legislature. Neither a Board resolution nor a consultation can manufacture regulatory jurisdiction over Africa. The bylaws cannot create criminal offences, police or prosecutorial powers, public punishment, confiscation authority, or a court with jurisdiction over the running Internet and underlying assets.

The instrument can locate private-company decision rights; it cannot enlarge those rights into governmental authority by vocabulary alone.

That distinction avoids two equally misleading conclusions. One is that the bylaws were merely internal and therefore did not matter. They mattered because records, membership, fees, meetings and corporate continuity matter to organisations relying on registry services. The other is that a document governing a regional technical coordinator must amount to a public constitution for the region. It did not. Its legitimate field, if properly adopted and applicable, was the company, its members, its contracts and the domestic legal framework around them.

This is why commencement deserves scrutiny as a control event. An effective date is not just a caption on a PDF. It determines which rules an organisation says it will use when identifying members, convening a meeting, running an election or authenticating an urgent action. A legible commencement record should allow an affected reader to move from the final text to the authority that adopted it, any member act required for constitutional change, the implementation instructions, and the transition from the previous structure. The 2012 materials show much of the destination. They are less complete about the bridge.

Membership as an operating architecture

Article 6.2 divided membership into three classes: Registered Members, Resource Members and Associate Members. This was not a description of three populations across Africa. It was a classification inside AFRINIC Ltd, attaching different positions to people or organisations in a private corporate framework.

Resource Member status was cumulative rather than automatic. Under Article 6.4, an applicant had to justify a need for Internet number resources, sign the Registration Service Agreement and pay the relevant setup and membership fees. Each element describes a distinct control point. Need justification links entry to the technical resource function. The agreement supplies a contractual relationship. Payment connects status to the company's fee system. The fact that these steps are stated in a constitution does not turn them into public licensing conditions.

They remain the terms through which a private registry company structured membership connected to its services.

The architecture matters because membership determines access to the institution's formal levers. Articles 7.1 through 7.6 gave Registered and Resource Members powers concerning meetings, election of directors, financial information, policy, constitutional change, auditors, special general member meetings and liquidation. These rights made membership a channel for company accountability. They also defined the limits of that channel: holding rights in AFRINIC's corporate process was not the same as holding political rights over a territory, an industry or the Internet.

Two provisions show how the text expected members to operate collectively. Article 7.6(vi) contemplated approval by Special Resolution when the constitution was revoked, amended or replaced. The bylaws defined a Special Resolution by a 75 per cent threshold. Article 7.6(viii), meanwhile, set a 5 per cent threshold among Registered and Resource Members for requesting a special general member meeting. One rule created a high bar for constitutional change; the other gave a smaller qualifying group a route to force an issue onto a formal meeting agenda.

Those mechanisms are consequential only if their procedural predicates can be checked. A percentage without a denominator, membership roll, notice record and tally cannot establish that a particular decision passed. No specific member Special Resolution adopting the 2012 text appears in the bounded public record examined here. That absence is not proof that no private record or legally sufficient act ever existed. It is a precise disclosure gap because the new constitution itself treated constitutional revocation, amendment or replacement as a matter for Special Resolution approval.

The distinction between participation and authorisation is especially important. AFRINIC said it received community comments and thanked the community. Comments can identify errors, improve clauses and expose trade-offs. They do not automatically evidence consent by every member, operator, state or African Internet user. Even strong support from visible participants cannot substitute for whatever formal act the applicable company rules and law required. Consultation and corporate authorisation answer different questions. A sound record should preserve both without laundering the first into the second.

Elections split across institutions

The bylaws did not hand the entire election process to one body. Articles 9 and 10 separated a Board-appointed Nomination Committee from an Election Committee designated by the chief executive officer from staff. In design terms, this divided candidate-related work from election administration. It also created an accountability map: if a nomination decision, administrative failure or unanticipated procedural question arose, the text indicated which institutional surface was implicated.

Paper separation, however, is not proof of practical independence or competent execution in any particular contest. A Board-appointed NomCom and a staff Election Committee remain products of specified appointment routes. The constitution can make those routes visible; it cannot prove how individual appointees acted, what information they received or whether a later election met every requirement. This article owns the operative design that began in 2013, not a judgment on any subsequent election.

Article 10.2 contained an unusually important rule for gaps. When an election issue was not expressly covered, members present would resolve it collectively, and the resolution would become precedent for future election guidelines. The provision joined immediate improvisation to future rulemaking. It gave the assembled participants a way to keep an election moving while requiring the answer to influence later guidance.

That mechanism has both a practical virtue and an accountability cost. Its virtue is resilience: no constitution can anticipate every disputed ballot, nomination or procedural edge case. Its cost is path dependence. A decision made by the members present at one meeting could shape future guidelines, so the attendance, question presented, answer and resulting update would need a clear record. “Members present” is also a bounded corporate constituency, not a sovereign public. Their ability to settle an internal election gap did not make them representatives of Africa at large.

The election design therefore illustrates the constitution's true scale. It was detailed enough to distribute responsibility and preserve an answer to unforeseen questions. It was not a grant of public electoral authority. That is exactly why its internal evidence should be strong. When a private institution performs an important technical function, traceable company procedure is more defensible than inflated claims of mandate.

Meetings turn authority into procedure

Article 11 required annual member meetings and annual public-policy meetings. It also provided for special member meetings and allowed urgent Board policy subject to later community endorsement. Article 12 then supplied the procedural machinery: notice, participation methods, quorum, polls, postal voting, electronic voting and proxies. Headline controls included 14 days' notice for an annual general member meeting and a minimum quorum of ten, read with the article's full conditions.

The proxy rules were not incidental. The text placed a five-proxy cap on each member in elections and barred candidates from carrying proxies. Those limits attempted to reduce concentrated delegated voting and a direct candidate conflict. They did not guarantee equal participation, validate any later ballot or establish that every interested operator could vote. They were internal safeguards within the membership structure the bylaws created.

Taken together, Articles 11 and 12 converted abstract member powers into an operating sequence. A right to elect a director means little without notice of the meeting, a rule for participation, a quorum and a method for counting votes. A right to call a special meeting requires a threshold and a procedure. A provision for urgent Board action needs a later accountability step if the organisation wishes to distinguish urgency from permanent executive discretion.

This procedural density strengthens the case that commencement mattered. From 1 January, AFRINIC said these were the rules through which member and policy deliberation would be organised. The organisation was not merely announcing values. It was identifying mechanisms capable of producing company decisions.

The same density raises the standard for the commencement record. If notice, quorum and voting are important enough to specify for member meetings, the decisive process that installed the constitution should also be reconstructable at an appropriate level. That does not require publishing confidential legal advice or every drafting exchange. It does require enough to identify the authorised organ, date, quorum or written-resolution basis, vote, relevant member act and relationship between final approval and the effective date.

Nine seats, introduced without a purge

Article 13.4 set out a Board of nine directors: six regional seats, two competency or non-regional seats, and the chief executive officer. The structure combined geographic allocation, skills-based flexibility and an executive seat. It was a company design for governing AFRINIC. The six regional positions did not turn directors into public representatives with political authority over their regions, just as the two competency seats did not create professional jurisdiction over an industry.

The important implementation choice was not to force the existing Board into instant textual conformity. AFRINIC's later preface explained that alternate directors would leave as their terms expired beginning in 2013, and that the Board was expected to correspond fully with Article 13.4 by 2015. The transition preserved term continuity while moving toward the new nine-seat map.

That choice deserves a fair reading. Immediate conformity might sound cleaner, but it could have displaced sitting directors at once and created avoidable continuity risk. A phased transition allowed institutional knowledge and fixed terms to run down over time. For a technical organisation whose members and operators depend on reliable administration, continuity is not an excuse; it is a legitimate design objective.

The June 2013 annual general member meeting provides a later implementation marker. Draft minutes record a vote to maintain the Article 13.4 transition referenced to Resolution 201211.160. This is evidence that the transition was not merely an explanatory footnote: members encountered it as an operative matter and chose to keep it. But the vote cannot be moved backward in time and treated as the original adoption of the bylaws. It occurred after the declared commencement and addressed maintenance of the transition.

Nor does the surviving record contain a seat-by-seat completion ledger. Such a ledger would name each alternate position, its term-expiry date, the corresponding departure and the point at which the Board achieved full Article 13.4 structure. Without it, the public can understand the intended mechanism and see an implementation vote, but cannot independently audit the entire 2013–2015 conversion from the materials gathered here.

This is a recurring distinction in the evidence. The mechanism is visible; completion is less so. The bylaws show the target Board. The preface explains the phase-out. The draft AGMM minutes show a decision to maintain it. What remains missing is a compact record that links each affected seat to the completed transition. Asking for that record does not reject phased implementation. It takes the transition seriously enough to test it.

Money, supervision and institutional memory

The constitution also placed ordinary but significant financial controls. Article 4 listed sources of funding and provided for Board review of fees. Article 15.3(viii) allowed directors to reduce or waive amounts, or amend payment conditions. These clauses located discretion over the financial relationship between AFRINIC and those subject to its membership or service arrangements.

Private fees can have serious consequences for an operator, but they are not taxes. A waiver decision can affect a member's position, but it is not a public pardon. A payment condition can be contractually enforceable without becoming a public penalty. Describing these controls accurately protects both sides of the boundary: it acknowledges their material effect while refusing to restyle corporate finance as sovereign fiscal power.

Articles 15, 19 and 23 located direction and supervision, Board meeting and voting procedure, minutes, authentication and urgent company action. The provisions gave the organisation ways to make and memorialise decisions. They are relevant here not because every clause needs a commentary, but because they show how much of AFRINIC's operating surface the 1 January commencement purported to organise. A constitution that specifies minutes and authentication recognises that authority depends partly on reliable evidence of acts.

Article 16 added a Council of Elders. The Council could contain no more than six former chairs and served in an advisory role. It offered institutional memory without a formal veto. Nothing in the provision made the Council a court, a sovereign council or an adjudicator. The title may sound elevated, but the function was bounded: advice from people with prior chairing experience.

The arrangement is a useful test of disciplined reading. Institutional names can imply more power than the underlying text grants. The correct method is to follow the operative verb. The Council advised. The Board directed and supervised through the company procedures. Members exercised specified rights through meetings and resolutions. None of these organs acquired power simply because AFRINIC's technical work was important beyond the company.

The chronology that will not resolve itself

The public adoption trail contains five markers that should fit into one sequence but do not yet do so.

First, a surviving later timeline says a first draft was published and an initial comment period ran from 7 May to 8 June 2012. The same timeline says the Board adopted the bylaws on 8 October and published them with a transition mechanism on 15 October. Yet the contemporaneous October announcement describes the first draft as having been published in June, already showing that the retrospective account and dated notice do not use precisely the same chronology.

Second, the announcement dated 25 October presented a revised timetable. Comments were to remain open through 9 November. The Review Working Group would review them from 12 to 19 November. Final Board review and ratification were scheduled for 20–25 November. Because this was a forward schedule, it proves what AFRINIC planned at that moment, not that each step later occurred. But it is difficult to reconcile with a statement that the Board had already adopted the final bylaws on 8 October unless “adopted” referred to an earlier draft, a preliminary act, or the later timeline was mistaken.

Third, Resolution 201211.160 declared a 1 January 2013 effective date and said the Board had reviewed community comments and the final version submitted by the Review Working Group. It thanked the BRWG, Me Ashok Radhakisoon and the community. This is the strongest official evidence of AFRINIC's asserted commencement and its account of who contributed. The public transcription, however, does not expose the signed original, the meeting or written-resolution date, attendance, quorum, proposer, seconder or tally.

Fourth, a preface dated 8 January 2013 says the Board approved the final text after two phases of community input and review. It also says that the bylaws took effect on 1 January. The source does not explain how final approval came seven days after commencement, whether the date reflects endorsement of a preface, retrospective confirmation, execution of an already completed act, or an error in the narrative.

Fifth, AFRINIC's Board page places the resolution beneath a February 2013 heading and marks it “Ratified in Feb13.” The page does not define the label. It could refer to ratification of the decision, approval of minutes, authentication of a record or an editorial classification. Those are possibilities, not findings. Without the underlying record, choosing one would be invention.

The archived 48-page PDF cannot settle the sequence by itself. It is titled “AFRINIC Bylaws 2012,” but contains no preface, adoption signature or express commencement clause. Its authority as the operative text is supplied publicly by the surrounding resolution and preface chain. That chain is enough to establish what AFRINIC asserted and the rules it presented. It is not enough to reconstruct one coherent adoption chronology.

The conflict must therefore be held open rather than dramatized. The dates do not prove fraud. They do not prove backdating, unlawful retroactivity or automatic invalidity. Corporate records can be produced, authenticated and summarized at different times. Retrospective web pages can compress stages. A later ratification may have a legally coherent explanation. But an explanation is not in the bounded public sources, and it should not be supplied by speculation.

What the public chain does and does not prove

The evidence proves several consequential propositions. AFRINIC publicly identified the 2012 bylaws as its new constitution. It declared 1 January 2013 as the effective date. It attributed the final text to Board review of community comments and Review Working Group work, and it acknowledged the BRWG, legal counsel and the community. The operative PDF contains a detailed private-company governance architecture. A preface explains the Board transition, and draft 2013 AGMM minutes show members voting to maintain it.

The sources do not disclose the original signed Resolution 201211.160 or the underlying Board record with date, attendance, quorum and tally. They do not disclose a specific member Special Resolution adopting or approving the constitutional replacement. They do not provide a Registrar filing, certificate or other statutory-compliance record for the 2012 text. They do not publish Me Ashok Radhakisoon's legal opinion or even an issue list showing which adoption questions counsel addressed.

They do not supply a complete final Review Working Group report, a full final-stage membership record, or a clause-by-clause matrix showing which comments were accepted, modified, rejected or deferred. They do not supply a clean final redline or the complete seat ledger for the Article 13.4 transition.

Some of those materials may properly remain private. Legal advice may be privileged. Drafting deliberations may be confidential. Data-protection or practical concerns may limit publication of participant information. The point is not that every internal document must appear on a website. The point is that a public claim of constitutional commencement should have a minimum evidentiary bridge that does not depend entirely on inconsistent retrospective summaries.

That minimum could be compact. A signed resolution or certified extract could state the authorised organ, date, meeting or written procedure, quorum, vote and legal basis. A member resolution could identify the relevant constitutional threshold if one was required and used. A Registrar receipt or certificate could establish the filing step, if applicable. A publication note could explain the relationship among adoption, approval, effective date and later ratification. None requires disclosure of privileged advice word for word.

The distinction between absence of evidence and evidence of absence is essential. This research is bounded by a defined set of public sources. A missing instrument in that set does not establish that it never existed in company archives, counsel's file or a government registry. It establishes that a reader cannot complete the chain from the public materials gathered here. That is an accountability gap, not a verdict on legal validity.

The strongest case for the 2012 process

The best bounded case for AFRINIC begins with practicality. Private membership companies routinely revise governing documents through iterative drafting. They need not publish every draft conference, Board discussion or privileged legal memorandum. AFRINIC invited comments, used a review body, acknowledged legal counsel, published a substantial final text, selected an effective date and explained a transitional mechanism. The rules themselves supplied considerably clearer architecture across membership, elections, meetings, voting, Board structure, fees, advice and company procedure.

The transition reinforces that case. Rather than dismissing alternate directors immediately to make the Board match Article 13.4 on day one, AFRINIC allowed terms to expire through 2015. That approach plausibly reduced disruption and preserved institutional memory. The later AGMM decision to maintain the transition suggests that members confronted the practical trade-off and chose continuity.

Aggregate process evidence can be enough for organisations to function. Members may have understood the operative rules. Staff may have known how to administer meetings and records. Counsel may have completed the legal work privately. The February label may reflect nothing more troubling than later minute ratification. Any fair assessment must leave those possibilities open.

But practicality cannot reconcile contradictory dates by itself. A process can be both operationally adequate and publicly under-documented. The existence of comments does not reveal their treatment. Thanks to counsel do not disclose the legal basis counsel considered. A working text does not identify the vote that installed it. Later implementation does not retroactively specify the original authorising act.

The demand for a minimum bridge is therefore not bureaucratic maximalism. It is a way to narrow the authority claim to what can be shown. AFRINIC could have protected privileged advice while publishing an authorised minute extract. It could have preserved participant privacy while issuing a clause-level disposition table. It could have maintained a concise transition schedule without exposing sensitive operational records. Each would have made the commencement more traceable without obstructing the company.

What a complete record would change

Counterfactuals help separate genuine accountability needs from requests for impossible certainty. Suppose a signed resolution and minute extract identified the date, quorum, vote and legal basis before 1 January. The effective date would then connect to an independently legible act even if counsel's advice remained confidential. The October, January and February markers could be described as drafting, formal adoption, publication or minute authentication rather than left in tension.

Suppose a proposal-and-comment matrix linked each major clause to an outcome: accepted, modified, rejected or deferred, with a short reason. “Community input” would become evidence about how the text changed, not a general legitimacy phrase. The matrix would not turn commenters into a sovereign electorate or bind every member. It would simply show whether the review process performed the function AFRINIC attributed to it.

Suppose a transition schedule named every alternate seat and expiry through 2015. The phase-in could be audited as a sequence rather than accepted as narrative. Readers could distinguish an authorised holdover from an unexplained mismatch between the old Board and Article 13.4.

The inverse counterfactual also matters. Had AFRINIC required immediate conformity on 1 January, the text might have aligned with the Board at once, but sitting directors could have been displaced abruptly. That might have increased continuity risk during a constitutional change. This is analytical, not a claim about what would certainly have happened. It explains why a transitional rule can be good governance even when the implementation record should be better.

These examples point to proportionate disclosure. The goal is not a documentary flood. It is a chain in which each consequential claim has an appropriate record: comments linked to review, review linked to a final text, the final text linked to authorised adoption, adoption linked to commencement, and commencement linked to a completed transition. The 2012 materials illuminate every link, but do not close them all.

Why operators should care without mistaking the power

For network operators, governance can appear distant until it changes a practical dependency. NRS describes AFRINIC in member-facing registry terms, while LARUS emphasises how governance choices around an Internet number registry can reach infrastructure continuity. The relevant lesson is not that every corporate dispute becomes an outage. It is that rules about membership, fees, authorised decision-makers and records sit upstream of services on which operators plan.

Predictability has operational value. A member deciding whether a meeting was properly called needs a known notice and quorum rule. A candidate needs to know which body manages nominations and which administers the election. A resource member needs to understand the relationship between need justification, the Registration Service Agreement and fees. Staff authenticating an urgent action need to know which company procedure governs. A director transition needs to show who held a seat at a particular time.

The private-company boundary makes these records more, not less, important. If AFRINIC cannot rely on sovereign status, its legitimate authority must be found in ordinary legal and institutional sources: its constitution, contracts, member decisions, Board acts and applicable domestic law. Accurate records demonstrate the path through those sources. Inflated language about community mandate cannot substitute for them.

This also explains why “community” must be used carefully. A technical community can offer expertise and valuable scrutiny. It can help a company detect bad rules before they become operative. But participation does not create a people, and endorsement does not confer regulatory jurisdiction. The quality of a consultation should be defended by showing who could participate, what they said, how the text changed and which authorised organ decided—not by implying that the process transferred public power.

On 1 January 2013, AFRINIC declared a substantial internal control system operative. Its scope was real: it touched membership, elections, meetings, finance, Board structure and institutional continuity. Its reach was bounded: it governed a Mauritius-incorporated private company and relationships falling within the relevant private and domestic-law framework. Keeping those propositions together is the clearest way to assess the event.

Commencement is a claim that should carry its own proof

The 2012 bylaws offered a recognisable operating constitution. They defined members and cumulative Resource Member entry conditions. They gave Registered and Resource Members meaningful corporate levers. They separated nomination from election administration, supplied answers for unforeseen election questions, and detailed meetings, ballots and proxies. They created a nine-seat Board while allowing an orderly phase-out of alternate directors. They located fee discretion, Board procedure, authentication and an advisory Council of Elders.

That was a consequential private-company control map, and the phase-in was a defensible continuity choice. The evidence supports AFRINIC's assertion that the text became operative on 1 January and that the transition was later maintained. It also supports the narrower finding that the public authority chain remains incomplete.

The chronology should not be forced into false coherence. An 8 October adoption, a 25 October announcement of future ratification, a 1 January start, an 8 January final approval and a February ratification label may have a sound explanation. The public sources do not give it. Nor do they disclose the signed resolution, decisive minutes or tally, specific member authorisation, public legal analysis, Registrar record, clause-level disposition matrix or complete transition ledger.

The missing material does not automatically invalidate the constitution. It does not prove misconduct. It tells readers where verification stops. AFRINIC proved what it announced and published; it did not publish enough to let the public reproduce the whole journey from consultation to authority and implementation.

The final limit is categorical. No corporate constitution, consultation, election rule or commencement date can create Africa-wide sovereignty. The bylaws could not confer regulatory jurisdiction, police or prosecutorial power, public punishment, confiscation or adjudicatory authority. They could organise AFRINIC Ltd. Precisely because that private role mattered to members and operators, its commencement deserved a documentary chain as carefully engineered as the control system it put into force.