Summary

  • Five days after an application was filed to end the receivership, the purported Board and receiver Gowtamsingh Dabee announced that they were working in close collaboration pending his formal discharge. The statement named important workstreams, but it was not a court order, delegation, bank mandate, signature schedule or responsibility matrix.
  • Later AFRINIC materials said some governance acts occurred with the receiver’s consent and that he continued approving number-resource allocations and assignments. Those admissions make the overlap operationally concrete: ordinary corporate claims, receiver powers and staff execution were active at the same time.
  • The sound conclusion is neither that every act of the purported Board has already been held void nor that collaboration proved its authority. No final public discharge order was located by the 10 August 2026 evidence cutoff, and each material act therefore requires a transaction-specific chain showing who could decide, veto, sign, pay, instruct and execute.
  • AFRINIC’s legitimate function remains narrow: it coordinates a technical ledger. Neither a purported Board nor a receiver may turn temporary control of that bookkeeper into sovereignty, ownership of operators’ address assets or a power to punish live networks.

The instruction nobody should have to guess about

Imagine the problem from the execution point rather than the press-release podium. An AFRINIC employee receives a direction affecting a registry entry, a contract or a payment. It comes from a committee associated with the group AFRINIC calls its Board. The receiver has not yet been formally discharged. Does the employee act immediately, seek the receiver’s consent, wait for two authorised signatures, or preserve the status quo? If the instruction is later challenged, which record protects the employee and the affected operator?

That was not an abstract problem after 13 October 2025. On 8 October, AFRINIC and Gowtamsingh Dabee had filed an application seeking termination of the receivership and his release or discharge. Filing an application is an act in a proceeding; it is not the requested order. Five calendar days later, the purported Board and Dabee issued a joint communique. They said they would work in close collaboration while he awaited formal discharge. They described work involving recruitment of a CEO, review of resources and member rights, litigation, audit and finance, policy structures, bylaws reform and external engagement.

The communique showed an intention to work. It did not disclose the operative rule for working. It did not identify, for each class of decision, the exact instrument conferring power, the initiator, the final decision-maker, a required concurrence, a veto, the signatory, the payment approver, the staff executor, the reviewer or the route for resolving conflict. It also did not state when any temporary allocation would begin or end.

Those omissions matter because consultation can inform a decision, collaboration can coordinate activity and consent can satisfy a condition, but none of those words, by itself, answers who holds the power to bind the company.

Two legal layers remained visible

The public record presented two power layers. In ordinary corporate operation, the Companies Act and AFRINIC’s bylaws describe responsibilities for a board, a CEO, committees and company administration. They place broad management or supervision, budget, spending, policy-facing guidelines, executive staffing and committees in the ordinary corporate layer. Day-to-day business would ordinarily sit with a CEO, while document execution follows specified signatory rules. Yet AFRINIC had no substantive CEO, and the 13 October statement said it had been nearly three years without one.

The receivership created a separate layer. Dabee had been appointed on 12 February 2025 in place of the Official Receiver, with the publicly stated aim of securing assets and seeing a Board reconstituted. Subject to the exact appointment instrument and any court order, section 190 and the Eighth Schedule of the Insolvency Act can give a receiver extensive powers over property, business operations, documents, proceedings, employees, agents and transactions, and can permit those powers to be exercised to the exclusion of a board.

That last qualification is decisive: the statute describes possible receiver power, but the exact appointment and variation orders determine its application.

No authenticated full text of the appointment order and all variations was located at a stable primary location in the research record. Nor was a comprehensive transition protocol found. The ordinary corporate rules therefore cannot simply be placed on top of the receivership and treated as self-executing; the receiver statute cannot simply be recited as though it discloses every later reservation and delegation. The missing bridge is instrument-specific.

The distinction between an application and an order remained live well beyond October. A public notice dated 29 October said the discharge matter was fixed for hearing on 26 November and established an intervention timetable. That was procedural notice, not a disposition. On 12 March 2026, AFRINIC said the application had been heard and judgment was awaited. It also said the group it called the Board was collaborating with the receiver pending formal discharge. By the evidence cutoff, the latest located AFRINIC case list continued to label the discharge application ongoing. No public final order granting or refusing discharge was located.

This is a bounded research result, not a claim that no non-public instrument exists or that no later order could exist.

Consent left fingerprints

The overlap was not confined to the language of a single communique. On 19 November 2025, an AFRINIC update said the Board, acting with the receiver’s consent, appointed an NRO NC/ASO AC representative. The same update announced an Interim Management Committee and a CEO Search Committee. In December, AFRINIC-36 took place with official material presenting both Board and receiver involvement. On 2 March 2026, AFRINIC said the Board, with the receiver’s consent, constituted and chaired a bylaws review committee.

Those express references to consent are evidence that the receiver’s position mattered for at least some acts. They do not reveal the general rule. A consent recorded for one appointment does not tell a member whether consent was compulsory for litigation instructions, policy ratification, a staff decision, a contract or a payment. Nor does the absence of the word in another notice prove that no consent existed. The necessary evidence is the underlying resolution, receiver instruction, delegation or court instrument for the transaction.

Resource operations make the same issue more immediate. AFRINIC said on 12 March 2026 that the receiver had been approving IP-resource allocations and assignments, while it presented the purported Board as addressing registry efficiency and while Board-labelled policy activity continued. Technical staff held the means of execution. This created three distinct points in a chain: claimed policy or governance direction, receiver approval of individual transactions and staff action in the registry. It would be inaccurate to say that Dabee personally made the technical changes; the public evidence establishes approval, not hands-on execution.

It would be equally inaccurate to treat the purported Board’s policy activity as proof that it could lawfully direct every resource outcome.

On 4 February 2026, the purported Board ratified an inter-RIR transfer policy and an abuse-contact policy. AFRINIC’s case list later recorded a March plaint challenging the transfer-policy ratification. The filing proves a challenge, not its merits and not a judgment invalidating the act. It does, however, demonstrate why transaction authority is not ceremonial. A disputed policy act can affect transferability, compliance exposure, transaction costs and the economic value attached to scarce address assets while adjudication remains unresolved.

Six separate answers were required

The transition needed a responsibility matrix across six surfaces, not a general assurance.

Staff and management. The ordinary corporate case points to Board direction of executive staff and CEO responsibility for day-to-day business. There was no substantive CEO, and the purported Board announced a CEO Search Committee and Interim Management Committee. The receiver side could draw, subject to the order, on powers to carry on business and engage or discharge employees. Joint CEO recruitment and staff participation in later committee work showed overlap. What remained unpublished was a staff reporting chart, the Interim Management Committee’s delegation, hiring and dismissal thresholds, offer authority, reserved matters and a conflict route. Dabee, the purported Board, the Remuneration Committee, the CEO Search Committee and the Interim Management Committee owed those records.

Number resources and technical registry operations. Ordinary rules can give a board policy-facing allocation responsibilities while staff provide registry services. Receiver powers may reach company operations, and AFRINIC expressly said Dabee approved allocations and assignments. Meanwhile, the purported Board reviewed rights and acted on policy, and staff held registry, RPKI and reverse-DNS execution capability. A resource-decision matrix, credential-custody schedule, delegation threshold, audit log, rollback rule and protection against unauthorised enforcement were missing. The receiver, purported Board and operational staff each occupied a different point in this chain and had to document it.

Litigation and legal representation. The 13 October statement gave the Legal Committee a stocktake and strategy role. Receiver powers can include bringing, defending and settling proceedings, appointing professionals and executing documents, subject to the appointment instrument. Dabee was also an applicant seeking discharge. Public material did not identify the client and instructing authority case by case, who retained counsel, who set litigation positions, who approved appeals, who controlled settlement or who paid. The receiver, Benjamin Mark Roberts as Legal Committee chair, the committee and external counsel needed a matter-specific authority record without disclosing legitimately privileged advice.

Policy and governance implementation. Ordinary bylaws support policy-facing Board and committee functions. The receiver’s court-created role was directed to preservation and reconstitution, not sovereignty over number resources, yet some later governance actions expressly relied on his consent. Board-labelled policy ratification, consent-conditioned appointments and the shared presence around AFRINIC-36 showed a mixed field. The missing proof was a reserved-matters list, consent form, minutes, votes, rights-impact assessment and rule for acting before discharge. The purported Board, Dabee and the relevant committees had to publish it; ecosystem bodies could not fill the gap through recognition.

Finance, audit, fees and banking. In ordinary operation, bylaws place budget, spending, fee and audit responsibilities in the Board layer. The purported Board created Finance and Audit Committees and reviewed financial statements. The receiver appointed Forvis Mazars, while receiver powers can reach property, contracts, borrowing, payments and professional appointments, subject to the order. An audit can report amounts, but it cannot prove the authority behind each retainer, invoice or payment. Bank mandates, payment signatories, approval thresholds, procurement records, auditor engagement, legal invoices and resolutions were required from Dabee, the Finance and Audit chairs and committees, and the company secretary.

Signature, seal, contracts and external representation. The bylaws ordinarily contemplate execution by the CEO, two directors or other Board appointees. The CEO office was empty. Receiver powers can include executing documents and using the company name, subject to the court order. Some notices were joint, some cited receiver consent, and others were signed by the purported Board chairman or issued by order of the Board. A notice’s signature does not prove the authority beneath it. Seal custody, contract and banking mandates, the two-signature rule during receivership, authorised spokespersons, the receiver’s veto and filing instructions remained to be shown by the receiver, purported chair and vice-chair, and company secretary.

The ledger boundary

These authority questions must not be mistaken for an argument that AFRINIC should wield a greater public power once the “right” office wins. The opposite is true. AFRINIC is a technical bookkeeper and ledger coordinator. Its defensible work is keeping unique and accurate records, maintaining contactability and relevant security metadata, isolating disputes, recording transfers and protecting continuity. It is not a sovereign, legislature, owner of operators’ address assets, punishment authority or source of universal mandate.

That boundary changes the impact analysis. When authority is uncertain, a routine act necessary to keep the ledger accurate may still need to proceed under a documented continuity protocol. But a contested policy, adverse resource intervention or asset-affecting restriction requires a far more exact chain of authority, procedure, liability and review. Geography is not title, a contact record is not obedience, a transfer record is not permission to control capital, and participation in a meeting is not collective ownership of every operator’s assets.

On 24 June 2026, NRS objected to the purported Board’s authority to call the 25 June AGMM, demanded transaction-specific authorization records and said a Companies Register filing was not judicial validation. Its controlling position is that election announcements and Registrar filings did not establish lawful Board authority while the receiver remained formally in office and litigation continued. It demands resolutions, delegations, bank mandates, receiver instructions and court orders. That position must not be diluted into one side of a rhetorical tie. It is also not a court judgment and must not be reported as one.

NRS advocates and represents explicitly authorised members; it does not operate the registry or its technical services. Heng Lu’s doctrine supplies the governing distinction between necessary bookkeeping and invented sovereignty. LARUS’s account likewise treats registry action as bounded by law and due process. Existing BTW analysis establishes the receiver-power and technical-continuity setting; the narrower problem here is the simultaneous control claim after 13 October.

What operators and members were being asked to risk

AFRINIC reported 2,506 active members at the end of 2025. The registry records underlying IPv4, IPv6 and ASN services, along with RPKI, reverse DNS and member service, make ambiguity economically relevant even while systems remain online. An operator planning deployment or financing needs to know whether an allocation, assignment, transfer-related decision or exceptional restriction will survive challenge. Delay or reversal can affect customer acquisition and infrastructure plans.

The risk is not that a database entry itself creates ownership; it is that control of a chokepoint can impose practical costs before a legal dispute reaches an answer.

Money exposes another edge. NRS tabulated USD 3,289,408 in legal and professional legal expenditure across 2022 through 2025, including USD 2,148,059 attributed to C&A Law for 2022 and 2023. Those totals make instruction, retainer, invoice and payment authority material to members. This article does not turn into a spending investigation, and an amount alone does not prove impropriety. It shows why an audited figure and a lawful authorization chain answer different questions.

Members also require protection against implied ratification. Attendance, voting or objection at a meeting cannot be converted into recognition of the purported Board, waiver of authority objections or retrospective approval of expenditures. Employees, vendors, counsel, banks and other counterparties need to know who can bind the company and what concurrence is required. Legal governance records should be disclosed without demanding publication of privileged advice. The objective is not maximum disclosure of litigation strategy; it is identification of the client, decision authority, mandate, spending approver and accountable record.

The best defence of the overlap is serious. The receiver’s purpose included restoring ordinary governance. The September election filled eight seats that AFRINIC presented as directors. An immediate freeze could have left the institution without strategic oversight or a substantive CEO. A staged assumption of responsibility, with the receiver retaining formal powers until discharge, could protect services and prepare handback. Express consent for some acts and continuing receiver approval of resource transactions can be read as safeguards rather than rivalry.

That defence justifies a designed transition, not an undocumented one. A staged handback has stages. It identifies reserved matters, delegations, concurrence, veto, signatures, bank authority, records and sunset. The public material showed selected examples of consent but not the rule explaining why one act needed it and another appeared unilateral. The defensible conclusion is therefore bounded: not every purported Board act has been adjudicated void, but transaction-level authority remained unproven in the public record.

The remedy is a published responsibility matrix. For each concrete decision class, it should state the legal source and exact clause, initiator, decision-maker, required concurrence or veto, signatory and seal holder, funding approver, staff executor and credential holder, independent reviewer, record location, escalation route, effective date and handback condition. Until a discharge and complete handback are proven, every purported Board act should identify its receiver or court interface, and every receiver act should remain within the lawful temporary mandate. Continuity protects operators when it makes authority legible.

“Close collaboration” did not.