Summary

  • Resolution 202006.558 records one clear institutional act: approval to reallocate a total of USD 71,217 from the MyAFRINIC and infrastructure budgets to the RPKI project budget. It does not reveal how that total was divided between the two sources.
  • A change in budget authority alters priorities and available options before it changes a service. Accounting execution, spending, implementation, acceptance, launch, adoption and measurable routing-security effect are distinct events, none proved merely by the resolution.
  • The strongest benign explanation is entirely plausible: AFRINIC may have identified a valuable RPKI requirement and uncommitted capacity elsewhere. That explanation becomes accountable when a concise record shows the baseline, source split, commitment check, scope, delivery evidence and later review.
  • AFRINIC’s useful role remains that of a private, membership-based technical bookkeeper and coordinator. Funding an RPKI project neither enlarges that role into public authority nor relieves the institution of the ordinary obligation to connect member-funded decisions to observable work.

L3 — The USD 71,217 decision and the missing source split

A precise act, not a complete account

The public starting point is unusually compact. AFRINIC’s register of Board decisions identifies Resolution 202006.558 in June 2020 and records approval for a budget reallocation to the RPKI project. The approved amount was USD 71,217. The money was to come from two named budgets: MyAFRINIC and infrastructure.

That sentence establishes a decision. It identifies the approving body, the month, the total, the destination and the source workstreams. Those details matter because they distinguish the event from a vague aspiration to support routing security. The Board did not merely express interest in RPKI; it approved a change in internal budget authority.

Yet the same sentence leaves the most elementary reconciliation unfinished. It gives one combined total, not two source amounts. The record available here does not say how much was removed from MyAFRINIC and how much from infrastructure. USD 71,217 therefore cannot properly be described as having come from MyAFRINIC alone, nor from infrastructure alone. It cannot be divided evenly as a convenience. No percentage burden can be attributed to either workstream, because neither the allocation between them nor their original budget denominators is established.

This distinction may look modest, but it is the first test of disciplined institutional reading. A round and plausible inference is still an inference. An exact total can create a false sense that every component behind it is equally exact. In reality, the combined figure is the point at which certainty stops. A reader can say that both budgets were named as sources and that the single authorised destination was RPKI. A reader cannot reconstruct the internal journal from that alone.

Nor does “from” necessarily tell us what eventually happened in the accounts. In a Board resolution, it describes the authorised budget movement. Approval may have been followed promptly by an accounting entry; it may have required further administrative steps; the project may have spent some, all or none of the revised authority by a later date. The available record establishes none of those alternatives. They are possibilities to be tested by later evidence, not conclusions concealed within the verb.

The same discipline applies to timing. June 2020 is the month in which the resolution appears in the Board register. It is not, without an execution record, an established date on which a cost centre changed, a supplier was paid, staff were reassigned, software work began or a production service changed. A calendar marker for authorisation should not be stretched into a chronology of delivery.

Why the number matters even when the outcome is unknown

The limited claim is nevertheless consequential. Budgets are instruments of choice. By approving the reallocation, the Board assigned greater budget authority to RPKI than the prior plan had provided and identified MyAFRINIC and infrastructure as the places from which the authority would be drawn. That is a visible prioritisation among internal claims on finite resources.

If the decision was executed as authorised, the amount available under the two source budgets would have been lower, in aggregate, by USD 71,217 relative to the previous internal plan, while the RPKI project budget would have been higher by that amount. This describes a change in authorised options. It does not establish that USD 71,217 was immediately spent, that assets of equivalent value appeared, or that the two source workstreams lost cash they otherwise would certainly have used.

The difference between authority and expenditure is central. A budget gives an organisation permission and capacity to pursue work within defined limits. An expense records that resources were actually consumed or committed under the applicable accounting treatment. A delivered capability requires still more: a coherent scope, people or suppliers, work, testing and acceptance. A useful operational result requires the capability to function in practice and to be used in ways that create the intended effect.

Collapsing those stages would make the resolution appear more informative than it is. It would allow supporters to cite USD 71,217 as evidence that route security improved, even though a budget allocation is not a technical measure. It would also allow critics to cite the same number as proof that member-facing or infrastructure work suffered, even though no revised plan or service consequence is established. Both readings skip the same missing middle.

Precision therefore cuts two ways. The amount makes it possible to ask a tightly bounded question: what changed because this exact authority moved? It also sets a limit on the answer: no effect should be assigned to the amount until the relevant financial, delivery and operational records join it to that effect.

Opportunity cost without an invented casualty

Every real portfolio decision has an opportunity cost. If additional budget authority is assigned to one workstream while the organisation’s total planned expenditure remains unchanged, another use of that authority is forgone or deferred at the planning stage. The resolution identifies where that adjustment was authorised: MyAFRINIC and infrastructure.

But opportunity cost is not the same thing as demonstrated damage. A source budget may contain uncommitted provision, a contingency, work that has become cheaper, or an activity whose timing can change with little consequence. It may also contain commitments that make a transfer difficult. The available evidence does not tell us which description fitted either source budget in June 2020. It does not show their original amounts, remaining balances, existing commitments, revised amounts, planned deliverables or actual outturn.

For that reason, the responsible formulation is conditional. If the reallocation was posted, it reduced the budget authority available to MyAFRINIC and infrastructure, taken together, compared with the earlier plan. Whether that reduced option value translated into a delayed feature, a cancelled purchase, a smaller reserve, a changed maintenance schedule, a later supplementary expense or no material service effect at all is unknown.

It would be equally wrong to assume that because no harm is proved, there was no trade-off worth documenting. Portfolio choices deserve an account precisely because their consequences can be subtle. A member portal may depend on scheduled improvements; shared infrastructure may depend on maintenance or resilience work; a reserve may protect future flexibility. Those are general examples of the kinds of option a budget can support, not claims about what MyAFRINIC or AFRINIC infrastructure lost in this case. The actual baseline and revised plan are needed to identify the real alternative use.

The missing source split compounds that uncertainty. Even if the combined reduction is known, the implications could differ depending on which budget supplied which amount and how large that amount was relative to its uncommitted balance. Without the split and denominators, there is no sound basis for calculating percentages, ranking the burden, or describing one source as the principal sacrifice. The arithmetical restraint is not pedantry; it prevents an unknown internal distribution from hardening into public memory as a fact.

The strongest benign explanation

The most favourable account of the Board’s choice deserves to be stated in full. AFRINIC may have encountered an urgent or newly defined RPKI requirement that was not adequately covered by the existing plan. MyAFRINIC and infrastructure may have held uncommitted capacity or lower-priority provision. Moving existing authority, rather than increasing the overall budget, may have been the quickest and most economical way to support a useful security capability.

That is a serious possibility. RPKI certification can provide valuable evidence about which autonomous system a resource holder authorises to originate a route. Better support for that function can be a legitimate technical priority for a regional registry. Internal reprioritisation can also be entirely ordinary management: circumstances change, project requirements become clearer and responsible organisations adapt their budgets.

Nothing in the short resolution disproves this benign case. Equally, the resolution does not establish it. The available record does not provide the business case, the alternatives considered, an uncommitted-balance check, a named owner, project scope, procurement or staffing choices, delivery milestones, acceptance criteria, launch evidence, adoption indicators or technical results. Plausibility is a reason to seek the connecting record, not a substitute for it.

Indeed, a sound decision benefits from disclosure more than a poor one does. If the source amounts were genuinely free of commitments, a simple reconciliation would show that the change did not displace contracted work. If the RPKI requirement was urgent, a concise statement of need and alternatives would explain why it outranked other uses. If delivery followed, dated milestones and acceptance evidence would convert intention into a traceable result. If the source workstreams absorbed the change without material disruption, their revised plans and later outturn could demonstrate that too.

The benign case is therefore strongest when it is auditable in the ordinary, non-accusatory sense: a member can follow the decision from the plan before the change, through authority and accounting, to work accepted and consequences reviewed. Accountability here does not begin with suspicion. It begins with the recognition that a private technical institution is spending and reallocating resources on behalf of a membership whose operations may depend on its continuity.