The Worked Run

One asset, carried from a corridor idea to a tokenized, operating terminal on live records in this ERP — and the roles that worked it.

The run

The Prairie Gateway Corridor was proposed and assessed as a land corridor across Alberta and Saskatchewan, its anchor asset named from the start. The Alberta Inland Port Rail Terminal — Phase 1, at CrossIron in Rocky View County, entered the registry and walked to Operating. Rocky View County came onto the Counterparties register as host municipality and walked to Operating partner; the Prairie Rail Cooperative engaged as terminal operator. The first GIS segment — the interchange lead — was surveyed, modelled, and its digital twin went Live. Earthworks tender TND-2601 drew three bids; they were levelled on weighted criteria and decided with reasons. The Canadian Transportation Agency’s construction authority and the provincial wetland approval were granted and confirmed In force, the wetland approval already flagged toward its renewal. Tokenization record ALC-REG-2601 was verified and issued against an independent appraisal plus audited cost basis. The first track geometry inspection was performed and verified. The assessment summary was filed to the vault — hashed, rewarded, queued for anchoring — and the services invoice for the whole programme was raised, sent and paid in core Accounting, its payment posted to a balanced journal. The canonical workflow, Asset Intake to Tokenized Operation, runs the same span as a governed process with its receipt on the CCJV hub.

The roles

The programme manager lives in the corridor read and the asset position: programme record versus registered reality, permits in force, operations open — the morning answer to “where does this programme actually stand,” computed from the records instead of assembled in a slide deck.

The asset operator works Operations and Permits: inspections scheduled and verified, renewals surfacing ninety days out, the asset’s history accumulating as evidence their counterparties can check.

The procurement lead runs tenders as pools: criteria published in the scoring, unscored bids flagged in the open, every decision carrying its reason — so the next tender draws serious bidders.

The counterparty never needs an account. The keyed asset view shows them the position — tokenization, procurement, permits, operations, documents by name and hash — while the files stay behind the uploader’s wallet, where the vault law keeps them.

What the run proves, and what it does not

It proves the system carries one asset end to end without re-keying: the corridor names the asset, the tender names the asset, the permits name the asset, the tokenization names the asset, and the asset position reads all of it back as one page. It does not prove a market, a return, or a second corridor — those are the programme’s next work, and they will be records here when they happen, not claims before they do.