System updates
Reference for the withdrawn Console screen that compared deployed system components with the reference directory.
The Console no longer offers the System updates screen. Its former Console URLs redirect to Organisation settings. The platform withdrew the system migration capability and the API routes behind the screen, so the screen does not return. The rest of this page records how it behaved.
System updates compared an organisation's deployed system components with the platform's reference directory. The screen applied changes to the organisation's system components as a whole. It did not provide a per-token setting.
Statuses shown by the withdrawn screen
The comparison table used these statuses:
| Status | Meaning |
|---|---|
New | The registry contained a component that had not been installed on the organisation's system. |
New version | A component was installed and a newer build of the same component was available. |
Unknown | The platform could not read enough of the component's on-chain state to compare it. The status did not mean that an upgrade was available or that the component was current. |
Legacy | A global compliance component was still bound to a superseded module family. |
Up to date | The deployed component matched the registry entry. |
The Legacy status applied only to global compliance modules. A legacy upgrade replaced the underlying compliance module family while keeping the organisation's configured rules. Components tied to one token or one instrument template did not use this status.
The screen also displayed a search field and two filters: Include experimental components and Show up-to-date components. Its summary ranked blocked authority, experimental updates, unverified components, an up-to-date system, and available upgrades in that order.
Upgrade behavior
Only an Admin or System Manager saw the upgrade control. The confirmation flow listed the components and affected tokens, required the text CONFIRM, and then required the wallet PIN.
Upgrade all applied every eligible component in one pass. It excluded experimental components unless the experimental filter was enabled, and it skipped work blocked by role authority. The affected-token count covered only components included in that run. Infrastructure add-ons that synchronized in the background did not appear as rows, but their changes were included in the summary and confirmation totals.
The confirmation screen warned that the upgrade was irreversible. During a running migration, the dialog could not be dismissed. If a migration failed, the screen displayed the completed and failed steps, the migration ID, and a retry control.
The screen had no single-component upgrade control. An ordinary component row showed its current and latest implementation addresses. A legacy row showed an explanation of the module-family replacement instead because it had no separate addresses to compare.