Two projects could publish the same allocation chart and release supply in very different ways. A useful release plan must therefore explain the journey from an intended allocation to a transferable balance.
Separate entitlement from transferability
Vesting describes how entitlement develops under the agreed conditions. A cliff defers the first vesting event. A lock-up restricts transfer and can operate alongside vesting. These terms should be written separately because an entitlement can exist while transfer remains restricted, and a release event may depend on more than elapsed time.
For a proposed adviser allocation, the relevant questions include when work starts, which deliverables count and what happens if the engagement ends. An attractive calendar cannot answer those questions unless the recipient agreement and release mechanism use the same definitions.
Name the authority that releases
A schedule should identify whether release is automated through a contract or depends on an authorised instruction. If people approve transfers, the process needs signers, checks and records. If software enforces conditions, its implementation needs review against those conditions. A spreadsheet can document a promise while leaving the actual transfer unrestricted.
The practical file should connect each recipient to the applicable agreement, relevant wallet and release rule. Sensitive personal information need not be made public to explain the method. Readers do need a coherent account of who can change a release and how that decision becomes visible.
Build the opening circulation statement
The proposed 25% sale allocation cannot be treated as the launch float. Different sale rounds may have different release terms; liquidity and other categories might also contribute transferable units. A defensible opening statement starts with the actual balances and applies a published classification consistently.
Suppose tokens move from one controlled programme wallet to another before distribution. That movement may be operationally necessary without increasing circulating supply under the chosen method. The report should explain the classification and avoid counting internal movements as new releases merely because a transfer occurred.
Publish the exceptions as well as the dates
A release table should show the opening position, scheduled changes, completed releases and unresolved differences. Departures, cancelled agreements and amended milestones can alter entitlement. The policy should say whether unearned tokens remain in the category, return to treasury or follow another approved route; ALFA has not yet fixed that policy.
The strongest update explains why the current position differs from the previous one. It does not need a price forecast. It needs enough detail for recipients, platform operators and readers to reconcile the promise with the operating record and understand the next event that could change transferable supply.
