Summary
- AFRINIC's crisis generated an understandable habit of measuring progress by the next hearing, return date, injunction, appeal, receiver appointment, or election deadline. Those events determined legal authority and constrained action, but they did not by themselves restore registry capability.
- A court calendar answers when a matter will be heard or when an ordered act must occur. A recovery plan must also state who owns each task, what completion evidence is required, which budget and dependencies exist, how member and operator rights are protected, and what happens when a milestone fails.
- The September 2025 board election was a major state change, not the end of recovery. The receiver still sought discharge, executive leadership remained unresolved, audits and financial approvals required work, allocation and membership questions remained, and litigation continued. AFRINIC needed a public recovery ledger running beside the docket, not a narrative built from court dates.
The docket became the institution's clock
When ordinary governance works, an Internet registry lives by operational clocks. Tickets arrive and close. Certificates renew. DNS and registration changes propagate. Accounts are audited. Budgets are approved. Directors meet. Executives make decisions. Members receive notice and vote. Incidents are detected, contained, and reviewed.
AFRINIC's crisis replaced many of those clocks with a judicial one. Attention moved to filing dates, appearances, interim orders, returns, appeals, receiver mandates, and election deadlines. Each court event could alter who was permitted to act for the company or whether a planned election could proceed. The next date on the docket became the most visible measure of movement.
That shift was not irrational. Once authority to act for the company was disputed, a technically sensible decision could still be legally ineffective. Courts supplied enforceable answers that internal bodies could not. They preserved the company, appointed temporary custodians, restrained contested acts, and directed a route back to elected governance.
The problem arose when legal movement was mistaken for institutional recovery. A hearing can be postponed while engineers keep systems running. A judgment can be delivered while the membership ledger remains unreconciled. A receiver can be appointed without receiving every credential, vendor contract, pending request, and security exception. A deadline can compel an election without completing audits or recruiting a chief executive.
The docket tells the parties when the court will address a legal question. It does not tell a member when a delayed allocation will be completed, who can approve a high-risk RPKI change, whether the latest backup was restored successfully, or how much money is reserved for continuity. Those are different plans.
AFRINIC needed both. Judicial supervision was part of the authority layer. A registry recovery plan had to translate that authority into operational work with evidence and failure consequences. Without the translation, every new court date created the appearance of progress while unresolved tasks accumulated behind it.
Court time and network time are structurally different
Courts are designed to resolve disputes fairly under law. Parties file evidence and submissions. Judges provide notice and an opportunity to be heard. Interim measures preserve positions where necessary. Appeals correct error and develop legal authority. The pace reflects rights, complexity, court capacity, and procedural fairness.
Networks run on a different timescale. A route leak can propagate in minutes. A certificate or key event can affect validation quickly. A failed authoritative service may need immediate response. A departing employee's credential should not wait for the next return date. A member's customer launch may have a commercial deadline outside the case timetable.
Neither clock can simply dominate the other. Speed without lawful authority can corrupt records or violate rights. Legal completeness without operational containment can allow avoidable technical harm. Recovery must connect them through pre-authorised emergency controls, preserved evidence, narrow stays, and escalation.
For example, a disputed resource transfer may require months of adjudication. The registry should not decide the ultimate claim through an emergency operational act. It can preserve the last verified holder state, block conflicting changes, maintain public services, record the dispute, and permit only security-critical adjustments under dual review. The court resolves the right; the continuity plan protects the network while it does.
Similarly, a court can order an election by a date. Election administrators still need a member population, eligibility rules, candidate timetable, voting system, data safeguards, challenge process, observers, tally controls, and handover. Judicial urgency defines the outer boundary. Operational milestones make compliance possible.
AFRINIC's long crisis showed the danger of asking one clock to perform the other's work. The court became the fallback for questions that a healthy constitution and board would ordinarily settle. Staff and members then had to fit technical and electoral work around litigation events. A resilient design would reserve courts for genuine rights and authority disputes while preserving enough standing capacity to keep routine service and recovery work moving.
The legal chronology was necessary and still incomplete as a recovery map
The public chronology contains decisive legal events. AFRINIC's board became inquorate in 2022. A 2023 Supreme Court judgment addressed board and member-right questions. In March 2023, proceedings sought preservation and receivership relief. On 12 September 2023, the Supreme Court placed AFRINIC in receivership with a preservation and restoration purpose. The 2024 Court of Civil Appeal judgment later restored that order after an authority-to-appeal dispute and substituted a finite period for completing the board-election route.
On 12 February 2025, Gowtamsingh Dabee was appointed to replace the Official Receiver. AFRINIC announced a June board election. On 13 June, an interim order restrained the announced electronic and in-person dates and directed compliance with the bylaws and earlier order. The matter was made returnable on 30 June. The election was later suspended and annulled. A further judicial extension produced a 30 September deadline for replacement elections.
The replacement ballot was completed in September. Eight directors were announced. On 8 October, the receiver filed an application for termination of receivership, according to the later joint statement. A decision was awaited, and the receiver continued supporting the board in the interim. Other proceedings remained active.
This chronology identifies changes in lawful authority and judicial constraint. It does not answer the operational questions that existed between the dates. What was the complete inventory transferred from the Official Receiver to the successor receiver? Which registry decisions were authorised during each period? Which requests were deferred? What funds and vendors supported the election and ordinary services? Which credentials changed custody? What recovery tests were performed? Which board capabilities were required before receiver discharge?
A legal timeline can state that the board was elected. A recovery map must state whether the board received complete records, accepted pending liabilities, restored committees, reviewed emergency delegations, obtained current financial information, and could supervise technical and member services safely.
The difference is not criticism of the courts. Courts cannot be expected to write an Internet registry's operating manual. It is criticism of any institutional narrative that uses the next judicial date as the whole plan.
A return date is not a deliverable
The June 2025 injunction made the election matter returnable on 30 June. A separate winding-up communication later said that petition was returnable on 24 July for AFRINIC to enter an appearance and state its position. Such dates matter procedurally. They tell parties when a response or appearance is due and keep a case moving.
They do not define a recovery deliverable. “Appear in court” is a legal task. “Restore reliable allocation handling” is an operational outcome. The first may support the second by clarifying authority, but one cannot be substituted for the other.
A proper deliverable has a scope, owner, acceptance test, and evidence. If AFRINIC says the member-service backlog will be cleared, the plan should identify which request classes are included, the baseline count and age, the responsible authority, the completion target, the oldest permitted unresolved item, and the public aggregate report. If it says financial reporting will return, the deliverable should name each outstanding year, auditor, board review, member approval route, filing obligation, and remediation owner.
Court calendars can even distort priorities. A task attached to an imminent hearing receives urgent attention because non-compliance is visible and consequential. A slower control failure, such as stale contacts or incomplete incident documentation, may receive less attention despite long-term risk. Recovery leadership must protect important work that lacks a judge's deadline.
The institution should therefore maintain two linked calendars. The legal calendar records cases, filings, orders, responsible counsel, potential operational effects, and next dates. The recovery calendar records workstreams, owners, resources, dependencies, target dates, evidence, risks, and failure triggers. Every legal event that changes authority updates the recovery plan. Every operational risk that may require directions is escalated into the legal plan.
The two calendars meet; they do not merge. That separation prevents litigation from becoming the only visible form of management.
Judicial deadlines are constraints, not implementation designs
The 30 September 2025 election deadline was valuable because it limited temporary authority. A receiver charged with restoring directors should not be able to extend the emergency indefinitely through internal announcements. An externally enforceable date created pressure to complete the core task.
But a deadline does not specify how to succeed. If the only metric is “election held by 30 September,” administrators can satisfy the date while unresolved questions remain about electorate completeness, candidate review, platform assurance, remedies, or handover. Conversely, a serious defect discovered near the deadline may require a short, reasoned adjustment to protect rights. A plan must say who can make that decision and what evidence is required.
Implementation begins by decomposing the final order. The authority workstream confirms who may convene, appoint committees, contract vendors, and certify results. The membership workstream reconciles the eligible population and issues member-level notices. The nomination workstream handles applications, vetting, conflicts, reasons, and appeals. The voting workstream secures the platform, access, secrecy, tally, and records. The legal workstream tracks orders and challenges. The communications workstream publishes changes without overstating conclusions. The handover workstream prepares directors to take control.
Each workstream needs intermediate dates earlier than the court's deadline. Delays need escalation thresholds. A missed voter-notice milestone may require more outreach. A failed platform test may require vendor replacement or a revised voting window. An unresolved candidate appeal may need independent review. A court application should be the last resort for a boundary dispute, not the first place administrators discover a dependency.
The June election's suspension and annulment showed what happens when a final date meets unstable intermediate authority and evidence. The replacement election narrowed representation channels and added clearer controls. Its success came from implementation work, not from the deadline alone.
Courts can demand an outcome. Institutions remain responsible for engineering a lawful, testable route to it.
Recovery requires named workstreams beyond elections
AFRINIC's board election received the most public attention because an elected organ was necessary to end the vacuum. A registry can elect directors and remain operationally unrecovered. The October 2025 joint statement acknowledged a large volume of unfinished work.
At least eight workstreams were visible.
Governance included board induction, committee creation, bylaws questions, policy bodies, member meetings, and the relationship with the receiver. Executive leadership included operating without a substantive chief executive, interim management, and recruitment. Finance included delayed audits, financial reports for 2022-2024, the unapproved 2021 statements, reserves, procurement, and legal expenditure.
Member and registry services included allocation questions, rights of members who joined after June 2022, backlogs, transfers, registration accuracy, and request authority. Technology and security included public services, credentials, RPKI, reverse DNS, IRR, RDAP, monitoring, incident response, and continuity testing. Legal included the existing case portfolio, the winding-up petition, election disputes, receiver discharge, and privilege.
People included staff authority, retention, workload, succession, and protection from carrying undocumented governance powers. External coordination included the NRO, ICANN, IANA functions, peer registries, government bodies, vendors, and the boundaries of each organisation's role.
These workstreams interact. A board cannot approve a stable budget without current accounts. A CEO search depends on the board's authority and clarity about receivership. A high-risk allocation may depend on legal advice, policy interpretation, staff capability, and review. An emergency continuity arrangement depends on contracts, technical tests, data protection, and member notice.
A recovery plan should assign an accountable owner to each stream and a coordinating owner for cross-stream dependencies. “The board” is too broad. A named committee or officer should report, while preserving collective duties. Temporary owners need end dates and handover obligations.
The plan should also separate survival tasks from institutional improvement. Restoring current registration accuracy is recovery. Rewriting the long-term policy model is reform. The emergency should not be used to rush permanent power changes before ordinary member accountability returns.
A milestone needs an acceptance test
Recovery language often relies on verbs such as resume, restore, review, strengthen, engage, and normalise. These words indicate direction but can remain true indefinitely. An acceptance test converts them into evidence.
“Board restored” could require eight elected seats accepted into office, quorum confirmed, conflicts disclosed, secure board access issued, induction completed, committees constituted, meeting schedule adopted, and authority boundaries with the receiver published. Not every item determines legal appointment, but together they show operational readiness.
“Receiver handback complete” could require a signed inventory of assets, contracts, credentials, court matters, pending decisions, member disputes, financial records, security exceptions, vendor access, and retained copies. The board should acknowledge receipt and identify any reservation. The court decides formal discharge; the institution proves the technical and administrative transfer.
“Member services normalised” could require published service classes, volume, age distribution, reason codes, oldest unresolved cases, decision authority, and an independent sample review. A low average is not enough if high-impact requests remain stuck.
“Financial reporting current” could require audited statements for every overdue year, board approval, member presentation where required, filing, publication, management responses, and tracked remediation. Appointment of an auditor is the start, not the finish.
“Executive leadership restored” could require a transparent search, documented criteria, conflict controls, appointment by competent directors, contractual authority, handover from interim management, and objectives tied to service and governance recovery.
Acceptance tests must be proportionate. Publishing sensitive credentials or member records would create risk. An independent reviewer can verify confidential evidence and publish a bounded conclusion. The point is not radical openness; it is verifiable completion.
When milestones lack acceptance tests, institutions can report activity as outcome. AFRINIC's recovery needed a ledger of completed states, not an accumulating list of announcements.
Budget is part of the plan, not an administrative detail
Every recovery promise consumes resources. Elections require platforms, communications, identity checks, observers, legal support, and staff time. Audits require fees and records preparation. Security remediation requires engineers and vendors. Litigation consumes counsel and management attention. Executive recruitment and retention cost money.
The court can order an act without setting the institution's complete recovery budget. The receiver and later board must allocate funds lawfully and protect continuity-critical expenditure. If they do not, a judicial deadline can displace essential service work or encourage an underfunded implementation.
AFRINIC's later annual report described improved reserves and liquidity through 2024 while acknowledging governance and operational strain. Financial capacity is useful. It does not show that money was allocated optimally or that the recovery portfolio was affordable under different litigation outcomes.
A public recovery budget need not reveal privileged legal strategy or security-sensitive vendor details. It can show categories: core registry operations, cyber security, elections, audits, executive search, legal matters, continuity testing, and contingency reserve. Members can then see whether exceptional spending is temporary and which service obligations are protected.
Each workstream should have a funding owner and a rule for overspend. If legal cost rises, who decides whether to reduce another programme? Which expenditure is ring-fenced because failure would threaten registry integrity? What insurance, reserve, or external support exists? Are peer-registry funds grants, loans, or conditional support?
Budget also disciplines scope. A plan promising every reform at once is not credible. Recovery should prioritise lawful authority, data integrity, public and member services, security, current accounts, and executive capacity. Longer-term policy and structural redesign can follow under ordinary governance.
Without a resource map, dates become wishes. A court calendar can compel urgency; a funded plan makes delivery possible.
Dependencies must be visible before they fail
AFRINIC's crisis repeatedly exposed hidden dependencies. An election depended on member contacts, corporate authority documents, committees, vendors, court orders, and physical or electronic voting arrangements. Registry decisions depended on staff, policies, executive or receiver authority, legal advice, databases, and security systems. Financial reporting depended on historical records, auditors, approval organs, and member meetings.
A dependency map lists what each milestone requires and identifies single points of failure. If only one employee understands a legacy registry function, that is a recovery risk. If one vendor controls identity verification without an export and deletion plan, that is a risk. If a high-risk resource change has no approver when the receiver is unavailable, that is a risk. If board access depends on credentials held by temporary staff, that is a risk.
External dependencies need legal boundaries. ICANN and the NRO can provide concern, expertise, coordination, funding, or technical support under their instruments. They do not automatically acquire power to run a Mauritian company or decide member rights. Courts can compel and review. They should not become default operators. Government inspectors can investigate under statute. Their role is not identical to the receiver or board.
The map should include time dependencies. Certificates expire. Vendor contracts renew. Court orders have terms. Director seats have tenures. Data-retention periods end. A plan that treats all dependencies as static will fail at the next date boundary.
Technical dependencies require tested alternatives. If RDAP and Whois share a database, their simultaneous availability is not independent resilience. If RPKI and member portals share identity infrastructure, one failure can affect both. If backups depend on the same legal entity and access chain, corporate failure may make them unusable.
Publishing a high-level dependency map helps members understand risk without exposing exploitable detail. Independent assurance can examine the sensitive layer. The aim is to discover the missing bridge before a court date arrives, not during the hearing that follows the failure.
Failure triggers are the difference between a plan and hope
Every recovery milestone can fail. A candidate process may attract too few qualified applicants. A voter register may contain unresolved disputes. A vendor may not pass security testing. An audit may find missing records. A CEO search may not produce an appointable candidate. A receiver-discharge application may remain undecided. A critical employee may leave.
A serious plan defines the failure trigger and response in advance. If platform testing fails by a specified date, activate the alternate provider or seek a bounded extension. If the member population cannot be reconciled, appoint independent review and publish the unresolved denominator. If a high-risk service has no lawful approver, preserve the last verified state and seek urgent directions. If the audit lacks evidence, issue a qualified account and remediation plan rather than waiting silently.
Triggers should be objective where possible. “When confidence is lost” gives too much discretion. “When two independent integrity checks fail” or “when a milestone is seven days late and threatens the final deadline” is more usable. Some judgments will remain qualitative, but the evidence and decision-maker can still be specified.
Escalation should be layered. Operational teams address routine deviation. A recovery steering body handles cross-stream risk. The board or receiver decides authority and funding changes. Courts receive genuine legal boundary questions. Members receive notice when their rights or material continuity are affected.
The plan also needs a stop rule. Emergency powers, consultants, and exceptional controls should end when their purpose is achieved. Temporary architecture often becomes permanent because no one defines exit.
AFRINIC's board election was a failure trigger for receivership transition, but not necessarily automatic discharge. The receiver filed a termination application and remained involved pending decision. A good plan would state the readiness evidence supporting discharge and the residual tasks assigned to the board.
Hope says the next date will resolve the crisis. A plan says what happens if it does not.
Courts should decide boundaries, not manage tickets
Judicial involvement became necessary because AFRINIC's ordinary authority failed and serious rights were contested. That does not make litigation the ideal administration channel for registry work.
Courts generally see the dispute presented by parties. They may not have the full operational portfolio. Evidence is shaped by pleadings, privilege, procedure, and the relief sought. A judge can issue precise directions, but repeated operational applications can slow both court and registry and place technical judgments into an adversarial frame.
The better design brings courts bounded questions supported by an operational record. Who may authorise this class of act under the receiver order? Does a proposed election step comply with the constitution? Should a disputed resource state be preserved pending trial? Has the receiver completed the conditions for discharge?
The registry should present the operational consequence honestly. It should identify which services or member rights are affected, available temporary measures, security implications, and the cost of delay. It should avoid using “Internet stability” as a universal argument for institutional preference.
Court orders should then be translated into an authority schedule readable by staff and members. If an order restrains one election date but directs compliance with the bylaws, the recovery body must identify the tasks that can continue, the tasks that pause, and the evidence needed for restart. It should not leave engineers and election volunteers to infer legal scope from headlines.
This separation protects judicial legitimacy. Courts remain the reality layer for enforceable rights. They do not become the help desk, change advisory board, or programme office. The institution remains responsible for competent execution and evidence.
The goal is not to keep courts away from Internet governance. It is to use them where law is indispensable while preventing governance failure from converting every routine dependency into litigation.
The board election was a gateway, not a finish line
The September 2025 election changed AFRINIC's state. A board existed where none had operated normally for years. The NRO welcomed the result and looked toward full restoration. The receiver later sought termination of receivership.
The October joint statement nevertheless listed continuing work. The receiver had not yet been formally discharged. Legal proceedings remained. The board was reviewing allocation and member-right questions. Audits for 2022-2024 were under way. The 2021 financial statements still required a member-meeting route after earlier rejection. Committees had to be constituted. Policy and external representation structures needed attention. A substantive chief executive was absent.
In November, the board announced an interim management committee and a CEO search committee, with receiver consent. It identified a six-month or CEO-appointment limit for the interim arrangement. This was recovery planning in embryo: an owner, scope, reporting relationship, and end condition.
The March 2026 member update still described efforts to restore full operational stability and address ongoing legal challenges. The later consolidated annual report framed 2022-2024 as a period of persistence under interrupted authority and presented financial and operational claims after the fact.
These developments do not diminish the election. They clarify its function. The board was the governance gateway through which ordinary accountability could return. Directors then had to accept, prioritise, fund, and close the recovery portfolio.
A public ledger should have followed that transition. For each workstream, it could show red, amber, or green status backed by evidence; the next milestone; owner; dependencies; member effect; and unresolved risk. Completed items should remain archived so later reviewers can reconstruct the path.
Without such a ledger, observers fall back to the docket and announcements. They know another case is pending or another committee exists. They do not know whether the registry is ready to leave emergency administration.
Handback requires proof on both sides
Ending receivership is not merely a court date. It is a transfer of control from a temporary custodian to elected corporate organs. Both sides need evidence.
The receiver should deliver an inventory of assets, bank authority, contracts, vendors, employees, credentials, data stores, backups, keys, pending member requests, resource disputes, court cases, insurance, tax and filing obligations, audit status, security incidents, temporary delegations, and unresolved decisions. Sensitive material can be controlled, but it cannot be absent.
The board should demonstrate capacity to receive it. Directors need secure access, conflict disclosures, committee responsibility, financial information, legal advice, and enough technical briefing to supervise without attempting to operate systems personally. They should accept the inventory with stated exceptions rather than issue a ceremonial acknowledgment.
Access should move under dual control. Temporary credentials and vendor permissions should be revoked or reissued. Retained copies should be declared. Emergency instructions should either be adopted under ordinary authority, replaced, or terminated. Pending decisions should have a named owner and deadline.
Independent assurance should focus on the highest-risk items: registry database integrity, RPKI and DNS authority, privileged credentials, financial control, and contested resource actions. The reviewer does not need to certify political wisdom. It should verify custody and control.
The court can then assess formal discharge with a stronger record. If residual tasks remain, the order or transition agreement can allocate them without leaving an ambiguous shared authority. If the receiver continues in support, the scope and end date should be explicit.
AFRINIC's October statement said the receiver agreed to continue supporting steps after appointment of directors pending formal discharge. That cooperation may have been prudent. A recovery plan would make the coexistence legible so staff and members know who can decide what.
The handback is complete when lawful authority, operational control, accountability, and records converge, not when an application receives a case number.
Member rights need their own service levels
Members experience recovery through decisions, not institutional milestones. A board can be elected while a member's allocation, transfer, contact change, or eligibility dispute remains unresolved. A receiver can be discharged while a backlog persists.
The recovery plan should therefore include rights service levels. Every member request receives acknowledgment, status, reason code, current authority owner, target date, and escalation route. A delay caused by litigation should identify the affected legal question without exposing privileged detail. A case requiring court direction should have a preservation measure.
Election and governance rights need the same discipline. Members should know meeting dates, voting eligibility, financial-statement status, committee vacancies, and how to challenge errors before votes. Board engagement should produce responses and decision records, not only sessions.
Aggregate publication should show request volumes, ageing, appeals, corrections, and exceptions. It should avoid using averages to hide old high-impact cases. Independent samples can test whether reasons match records.
The plan should distinguish member and operator urgency. A routine billing correction can follow a normal queue. A change affecting route security or live customers may require expedited review. Priority rules should be public enough to prevent influence from replacing evidence.
This is where the Number Resource Society's future direction is constructive. Operator rights, collective accountability, auditability, and portability give members protection that does not depend entirely on the speed of one registry's corporate recovery. If the institution cannot deliver a critical registration function, an authorised alternative should preserve continuity without forcing renumbering or surrender of the resource.
Portability is not a shortcut around lawful disputes. A contested claim must travel with its dispute state, and uniqueness must remain protected. It is a safeguard against making customers wait for institutional recovery when another competent registry service can maintain the ledger.
A court calendar protects procedural rights in litigation. A member service level protects operational rights while litigation continues. AFRINIC needed both.
Recovery reporting should separate facts, claims, and forecasts
Crisis communications often collapse three categories. “Services are stable” may be a measured fact, an institutional assessment, or a forecast. “The election will restore legitimacy” is a forecast. “The court appointed a receiver” is a legal fact. “The receiver will complete recovery by a date” is a plan claim.
A recovery ledger should label them. Verified facts carry evidence and date. Institutional claims identify the speaker and measurement. Forecasts state assumptions and confidence. Risks identify triggers and response.
This discipline would have improved AFRINIC's public account. A court order could be linked directly. A service-continuity claim could specify endpoints, probes, ticket data, and limitations. An election date could show prerequisite status. A receiver-discharge application could be distinguished from an order granting discharge. A committee announcement could state pending deliverables rather than imply completion.
Uncertainty should be visible. If a police investigation or court challenge prevents a conclusion, the report can state what is known, what remains unresolved, and which temporary control protects members. Silence encourages speculation; overstatement damages trust when the next filing changes the picture.
The ledger should preserve history rather than overwrite pages. Superseded dates and rules are important evidence. A reader should be able to see which version controlled at a given time and why it changed.
This is not public relations. It is institutional memory. Directors, staff, members, courts, and successors need a common account when personnel and authority change.
Recovery ends gradually. Clear classification lets the institution report progress without pretending that the crisis is either fully resolved or permanent.
A practical registry recovery ledger
A usable ledger can be compact. Each row contains the workstream, outcome, accountable owner, authority source, baseline, target, due date, budget status, dependencies, evidence, current state, member impact, next decision, and failure trigger.
For governance, the outcome might be “ordinary board authority operating without receiver consent.” Evidence would include court status, board quorum, committee mandates, and revoked temporary delegations. For executive leadership, it might be “substantive CEO appointed and interim committee closed.”
For finance, rows would cover each overdue audit and member approval. For member services, rows would cover backlog classes and high-risk decision authority. For technology, rows would cover service availability, data reconciliation, recovery tests, credential custody, and incidents. For legal, rows would record each matter's operational exposure without publishing privileged strategy.
For elections and membership, rows would track the member denominator, register assurance, challenge handling, and permanent election record. For continuity, rows would cover backup custody, substitute-service tests, member notice, and portability readiness.
The status should follow evidence, not management sentiment. Green means the acceptance test passed. Amber means delivery remains possible with named risk. Red means the trigger fired and escalation began. A missed court date may make a row red, but so may a failed restore test or aged member request with no lawful approver.
Members should see the public layer and receive more detail for their own cases. The board and receiver see the full management layer. Independent reviewers and courts receive controlled evidence according to role.
The ledger's value is not visual sophistication. It forces the institution to define recovery as a set of observable states. A new hearing updates the relevant rows; it does not become the report's organising principle.
Had such a ledger existed from 2022, AFRINIC's stakeholders could have distinguished legal preservation, service persistence, election preparation, corporate handback, and long-term reform. They would have known where delay actually lived.
What the record supports
The public evidence supports the conclusion that courts were indispensable to AFRINIC's governance restoration. Judicial orders preserved the company, addressed authority, installed or maintained receivership, restrained contested election steps, imposed completion periods, and later supervised aspects of the replacement election. Without that authority, the company lacked an uncontested internal route back.
The same evidence supports the conclusion that legal milestones did not equal full recovery. The first 2025 election encountered injunction, uncertainty, suspension, and annulment despite a public timetable. The replacement election produced a board, but the receiver still sought discharge and remained involved. Audits, financial approvals, executive recruitment, member and allocation questions, committees, legal matters, and policy structures remained active work.
The record does not show every private recovery plan AFRINIC, the receiver, staff, or advisers may have used. Some operational inventories, budgets, risk registers, and security tests may exist confidentially. Their absence from public material is not proof that no work occurred.
The governance defect is that members and affected operators could not evaluate recovery from a joined, evidence-based ledger. They were left to infer institutional health from notices, court events, service persistence, and later retrospective reporting.
The remedy is not to ask judges for more operational detail. It is to require the company and temporary custodian to translate judicial authority into owned work, funded milestones, acceptance tests, member remedies, and failure triggers.
Courts decide law. Receivers preserve and administer within mandate. Directors govern. Executives manage. Staff operate. Members authorise and hold the institution accountable. Operators keep networks running. A recovery plan makes those boundaries and handoffs executable.
The next court date may matter greatly. It should never be the only answer to the question: when will the registry be recovered?
Sources and analytical limits
The AFRINIC Constitution 2020 supplies the ordinary allocation of powers among members, directors, election bodies, and management. It does not resolve every receivership-era authority question.
The Supreme Court judgment in Benjamin Adzenyamebeye Eshun v African Network Information Centre (AfriNIC) Ltd, 2023 SCJ 63, the 12 September 2023 receiver order, and the Court of Civil Appeal judgment 2024 SCJ 473 support the board, authority, preservation, receivership, and election-completion chronology. They are not operating plans for registry recovery.
The receiver's 21 April 2025 election communique, the 13 June interim order, the annulment notice, and the 30 June update establish the announced date, judicial interruption, annulment, and replacement deadline. They do not determine the merits of every election dispute.
AFRINIC's 14 July 2025 winding-up communique is used only to illustrate the distinction between a case return date and registry recovery work. It does not support a conclusion on the petition's merits or outcome.
The replacement election guidelines, 5 September order, and September result announcement support the election deadline, external-supervision, and board-reconstitution chronology. They do not independently certify every member, candidate, or platform decision.
The 13 October 2025 joint statement, 19 November board update, and 12 March 2026 member update support the continuing receiver, leadership, audit, legal, membership, allocation, committee, and institutional-stability work after the election. They are official accounts and are not treated as independent proof that every recovery claim was achieved.
AFRINIC's Consolidated Annual Report 2022-2024 supports the retrospective description of governance uncertainty, interrupted authority, slow approvals, operational persistence, and financial position. Its publication in 2026 does not replace contemporaneous service, customer-impact, or recovery evidence.
The article did not have access to the complete court docket, sealed filings, privileged advice, receiver reports, private board papers, security architecture, credential inventories, vendor contracts, recovery budget, member-ticket ledger, audit working papers, or a final judicial determination of every later dispute. Proposed workstreams, milestones, acceptance tests, and failure triggers are governance standards derived from the public record, not claims that AFRINIC had no confidential planning and not legal advice on any pending case.