Summary

  • Resolutions 202108.626 and 202108.627 form a paired authority record: the first endorses and ratifies action described as already taken for SC/COM/JICA/000471/2021, while the second authorises Nirmal Manic to represent AFRINIC, affirm affidavits and perform connected acts.
  • The strongest benign reading is that a provisional-attachment emergency compressed the normal approval sequence, requiring quick preparation of documents and a clear corporate representative. Express Board alignment could reduce internal uncertainty without implying that anyone had acted unlawfully.
  • The strongest challenge is evidential. The published resolutions do not disclose the pre-existing delegation instrument, exact sequence of preparation and filing, meeting day, quorum, vote, conflicts, limits or legal advice. Later endorsement therefore cannot make the earlier authority state fully reconstructible.
  • On 13 August 2021, the Judge in Chambers held the section 806 application misconceived, identified main levée or cantonnement in validation cause SC/COM/JICA/000476/2021 as the available routes at that stage, upheld Cloud Innovation’s preliminary jurisdictional objection, and set aside application 471 with costs. The order did not decide ratification or internal corporate authority.
  • A proportionate safeguard would be a contemporaneous emergency-litigation authority receipt: a concise record of the trigger, delegation, agents, acts, limits, timestamps, Board review and external procedural status. It would preserve speed while preventing a later resolution from becoming a substitute for history.

L3 — The resolution that arrived after the action

The important verb in Resolution 202108.626 is not simply “authorise.” It is “ratify.” According to AFRINIC’s published Board record, the Board had been informed on 23 July 2021 that Cloud Innovation Ltd had sought and obtained a provisional attachment order against AFRINIC. The record also says that the Board had previously been apprised of other cases initiated by Cloud Innovation that management was resisting before the Supreme Court of Mauritius.

Against that background, the Head of Finance and Accounting, acting with authorisation from the Chief Executive Officer, had taken action to prepare relevant documents for an application to vary the attachment order while Cloud Innovation’s validation application remained pending. Only then does the published resolution say that the Board fully endorsed and expressly ratified the described action, including incidental action executed on AFRINIC’s behalf, for SC/COM/JICA/000471/2021.

That is a backward-looking act. It records a Board position about conduct that the resolution itself describes in the past tense. Resolution 202108.627 then changes direction. It says urgency required an application seeking the removal or reduction of amounts frozen following the attachment order dated 23 July 2021. It authorises Nirmal Manic, identified as Head of Finance and Accounting, to represent AFRINIC for the application, affirm affidavits and perform other acts required in connection with it. This is prospective authority directed toward an identified officer and a defined piece of litigation.

The distinction is more than grammatical. A record that management had been responding to litigation is not the same thing as a record that the CEO authorised document preparation. Preparation is not automatically filing. Filing is not automatically representation. Representation is not automatically authority to affirm an affidavit. And the Board’s later endorsement is not the same event as the earlier executive decision. Resolution 202108.626 and Resolution 202108.627 bring those elements together, but they do not erase their sequence. Careful institutional analysis must keep each act in its own time.

Even the identifiers require that discipline. The operative headings read Resolution 202108.626 and Resolution 202108.627, and those are the identifiers that control this analysis. Yet the surrounding public record is not internally neat. The selected manifest calls the pair 202107.626-.627, while the archived page places the resolutions in its August 2021 section but labels the relevant links 202104.626-.627. The disagreement among July, April and August-style prefixes is a record-quality fact. It is not evidence of misconduct, and it does not justify guessing an internal meeting date.

It does, however, show why an operative heading, a meeting timestamp and a stable register entry should be preserved as separate fields rather than treated as interchangeable.

The exact meeting day is not established in the available record. Nor is the moment at which document preparation became execution, the point at which application 471 was filed, the time an affidavit may have been affirmed, or the date of service. The public resolutions do not supply a pre-existing CEO delegation instrument or a management authority schedule. They do not disclose Board attendance, quorum, vote, dissent, conflicts or recusals. Nothing in the available material establishes whether directors regarded ratification as legally required or whether they chose it as prudent confirmation against possible challenge.

The absence of those documents from the public record does not prove that no private record existed. It means only that a reader cannot use what is public to reconstruct the whole authority chain.

That limitation matters because “ratification” can tempt an observer toward a conclusion the record does not support. A later endorsement may be consistent with concern about earlier authority, but it does not prove earlier authority was absent. It may be designed to remove doubt rather than cure a defect. It may confirm a broad delegation already in force, provide litigation-specific assurance, or clarify who may take the next step. The resolution’s retrospective form is significant because it shows that action came first and express Board endorsement came later. It is not a judicial or statutory finding about the status of the earlier act.

The Board record itself offers a substantial explanation for the compressed sequence: urgency. An attachment affecting a company’s funds can put pressure on ordinary decision time. A company facing such a situation may need to obtain legal advice, assemble documents, preserve deadlines and identify a person capable of giving evidence before a full collective record is published. BTW’s earlier examination of the account attachment supplies the limited operational context needed here: restrictions on accessible funds can place continuity under strain. That context explains why speed might matter.

It does not establish an amount frozen, a particular missed payment, a specific outage or the merits of either party’s claim.

The strongest benign reading therefore starts from institutional realism. The CEO authorised a finance officer to prepare relevant documents; management and finance action began; the Board, once engaged through the published pair, aligned the corporate principal with the acts described and made future representative authority explicit. Naming Nirmal Manic and the acts he could perform reduced ambiguity about who might speak and affirm evidence for AFRINIC. On that view, the resolutions are a bounded repair to the clarity of a private company’s litigation authority.

They show directors attempting to put the company behind urgent agent action and to state who could carry the matter forward.

That reading does not need an accusation to be meaningful. Emergency governance often has to reconcile two valid needs: action before harm compounds, and review before exceptional conduct becomes unbounded. Waiting for every ordinary step may be costly when a legal deadline or operational constraint is immediate. Acting first without a visible limit may create a different cost, because members, directors, counterparties and a court may be unable to tell who was empowered to do what. A retrospective resolution can reduce that second uncertainty by declaring the principal’s later position.

It can also prevent disputes within the organisation over whether an agent continues to speak for it.

But the strongest challenge begins at exactly the same point. A public resolution that says action was ratified establishes later endorsement; it does not show the reader the authority state at the instant of action. The underlying delegation could have been broad, narrow, conditional or absent. The “action” could have consisted only of preparing papers, or could have extended to steps not separately itemised in the published wording. The resolution’s reference to incidental action broadens the description without supplying a ledger of acts.

Without timestamps, the reader cannot establish what happened before the Board acted, what happened after it acted, or which steps depended on Resolution 202108.627.

Nor does the public wording explain the limits of the authority granted. It identifies the case and functions of representation and affidavit affirmation, but it does not publish a financial ceiling, expiry, reporting deadline, counsel instruction, or condition tied to a particular procedural outcome. It does not say whether a fresh Board decision would be required after an adverse order. It does not record whether directors were notified immediately when action began or only once papers were already advanced. These may all have been handled privately.

Their public absence nonetheless means the resolution cannot bear the weight of a complete audit trail.

The right conclusion at this close level is modest. The pair is neither empty ceremony nor proof of a completed legal cure. Resolution 202108.626 publicly places the Board behind action described as already undertaken for application 471. Resolution 202108.627 publicly names an officer and the connected acts he may perform. Together they improve the visibility of AFRINIC’s position after the action sequence had started.

They do not establish that the original action was invalid, that ratification was necessary or sufficient under Mauritius law, that every relevant director participated without conflict, or that any court accepted the internal arrangement.

That modest conclusion is already useful. It tells members and operators where to direct questions. Which delegation existed before 23 July? When did the CEO give authority? Which documents were prepared, filed and served, and when? When did directors meet? What exactly did they understand themselves to endorse? Which future acts fell within Nirmal Manic’s mandate? The closer the record comes to answering those questions, the less pressure anyone must place on the single word “ratify.”