Tender & Tokenize

Procurement decides who builds, on criteria stated before the bids land. Tokenization records what was issued, against an asset that earned it. Both run on reasons written down.

Procurement & Tendering — levelling, not lowest-price

A bid record carries the tender reference, the asset, the bidder, the scope bid, the amount, and a weighted score with the criteria notes behind it. Bids walk Submitted → Under review → Levelled, and end Awarded, Declined or Withdrawn — every ending with its reason in the award note. The levelling assist reads the pool as a pool: the spread between low and high, the flags that matter (a bid with no weighted score, no criteria notes, or no stated scope is flagged in the open), and the score leader named as exactly that — the leader on criteria, because price alone does not award.

On the worked run, three earthworks bids landed on one tender. The lowest price was not the award: its criteria notes showed thin rail-specific experience for a live-terminal interface, and the record says so. The award went to the highest weighted score, with the reasoning — complete drainage plan, verified rail references, the mid price buying the thinner-risk programme — written on the winning record. The third bidder withdrew before award when its surety line was reduced; that, too, is on its record. A bidder who loses on this system can read why. That is not courtesy; it is what keeps good bidders bidding.

Asset Tokenization — verified before issued

A tokenization record names the asset, the valuation method (an independent appraisal, an audited cost basis — a stated method, never a promised price), the registry reference, and the issuance itself. It walks Draft → Verified → Issued → Active, with Issued as an approval state: verification is a step a person takes, not a status a record drifts through. A suspended issuance is an exception state, named as such.

Participation: the record’s stated value sets the gate. To participate in a tokenization, a wallet holds ALC equal to 1% of that value — the same 1% pattern as project participation, converted at the reference price and stacked across the wallet’s tokenizations. The gate is checked fresh when the wallet joins and read continuously after: a balance that drops below the stacked hold suspends the participation until the hold is restored, and a participant can leave at any time. Using the Tokenization module itself stays at the standard module hold — 1 ALC; the 1% gate governs participating in an issuance, not keeping the registry.

What tokenization means here, precisely: a registry record that an identified asset, valued by a stated method, has a stated issuance against it — checkable by any counterparty through the asset view. What it never means: a yield, a return, a price path. The token is utility — it gates the ERP’s modules and settles the vault’s economics — and the asset’s performance is the asset’s business, recorded in Operations, not promised in Tokenization.