Strategic partners receive 15% in ALFA's indicative allocation. The category can support relationships that expand service capability, but a label does not establish what any recipient must deliver. Each future award should connect the relationship, contribution and release conditions closely enough for the programme to explain why those resources were committed.

Define the contribution before the award

A partner might provide an integration, distribution capability, operating access or another agreed service. Those contributions are different and require different evidence. The agreement should identify the responsible entity, deliverable, timing and acceptance process. An introduction may be valuable without being equivalent to a completed commercial contract. A broad strategic relationship should therefore not conceal an award whose underlying obligation is modest or uncertain. The allocation record should identify the purpose clearly enough for an authorised reviewer to assess whether the amount and conditions correspond to the contribution the programme actually expects to receive.

Test the dependency with a scenario

Imagine a hypothetical partner promising access to a training provider. If the provider agreement is never executed, the programme should already know whether the award remains earned, is reduced or does not release.

If the partner instead delivers a functioning integration, acceptance should examine the integration itself. The release schedule should track the relevant contribution rather than an unrelated calendar date. These distinctions protect both sides: a recipient can understand how to earn the award, and the platform can explain the resulting distribution without relying on vague expectations that changed during the relationship.

Separate endorsement from obligation

Using a partner's name publicly requires an accurate description of its role and status. An intended supplier, signed adviser and operating partner should not appear interchangeable. ALFA's source materials already distinguish proposals, non-binding letters and documented institutional relationships. The same discipline should govern token awards. Receiving an allocation should not be presented as evidence that the recipient guarantees the whole programme or endorses every claim made about it. The contract should also address confidentiality, permitted publicity and what happens to public references when the relationship ends, keeping the narrative aligned with current responsibilities.

Reconcile relationship changes

A partner may change scope, fail to perform or complete its work earlier than expected. The programme needs an approval process for amending the award and a record of vested, released and unearned amounts. Any reallocation should follow the final authority and disclosure rules rather than disappear into another category. A credible partner category would show how distributions follow documented contributions and how exceptions are handled. That makes strategic participation assessable through delivery, while preserving the distinction between a commercial relationship and rights held by ordinary token users.

References
  1. ALFA expanded development whitepaper ↗
  2. ALFA token framework ↗