Skip to main content
development environment — data here is not real and actions have no financial effect
Platform

Asset Lifecycle

Issuance is a day. Servicing is a decade. The arithmetic that goes wrong is the arithmetic that runs every quarter across a register that keeps changing.

What it changes

  1. Distributions pay holders of recordThe register is rebuilt from confirmed movements as at the record date, not read from today’s holdings. Paying today’s register for a record date three weeks ago pays the people who bought since and not the ones who sold.
  2. The pool is split exactlyLargest-remainder allocation means the lines sum to precisely what was funded. Rounding each share independently leaves the issuer a few minor units out every cycle, and across a thousand holders and twelve months that is a break nobody can explain.
  3. A split is planned before it is appliedA unit adjustment rewrites every position at once, so it is computed, previewed, hashed into the approval, and re-checked against the register at execution. A ratio that does not divide some holding exactly is refused, naming the holders it fails on.

What it includes

DistributionsRecord dates, per-holder withholding, exact allocation, per-line payment.
Corporate actionsSplits, consolidations, votes, notices, maturities and wind-downs.
RedemptionsEligibility, pricing at a supplied valuation, burn and payable in one transaction.
WithholdingRecognised as its own liability and remitted with its own reference, so a balance that never clears is visible.

What this deployment does not do

Stated plainly

There is no per-jurisdiction withholding matrix: one rate is set per run and applies to every holder. Votes can be announced but not yet cast or tallied.

See it against something real.

Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.