This page walks through three workflows from the Canton hub: DvP readiness, repo collateral mobility, and capital efficiency. It is written for settlement and collateral practitioners who want to see what each step checks before running the tools themselves. Every step links the tool that runs it, and every workflow links its chain page on the graph, so a reader can reproduce each run in the browser and check the artifact it emits.
On AINumbers, a workflow is a fixed sequence of browser tools: each step runs one tool, and each run emits an artifact whose execution_hash is carried into the next step, so the whole run can be re-verified end to end.
The three workflows live in the Canton hub's flow map and in chaingraph.json. Each one is a chain page on the graph; this page is the guided tour of what its steps actually check.
List the steps of the canton-dvp-readiness workflow and say what each step validates.
Delivery-versus-payment settles only if the asset leg and the cash leg complete together. The Canton DvP Atomicity Validator checks that pairing on a synthetic transfer, and the Tokenized Collateral Eligibility Checker confirms the asset leg is eligible collateral in the first place.
Run the two tools in order on synthetic inputs and the workflow's chain page, canton-dvp-readiness, records both artifacts with their parent hashes, so a reviewer can replay the pair and reach the same verdict.
Run the Canton DvP Atomicity Validator on a synthetic DvP pair where the cash leg fails, and quote the decision and execution_hash.
Moving collateral into (and out of) a repo on-chain has three questions: what haircut applies, whether the package is eligible, and whether the cash leg actually reached finality. The workflow chains the On-Chain Repo Haircut Calculator, the eligibility checker you met in step 2, and the On-Chain Cash-Leg Finality Checker.
The chain page is canton-repo-mobility. Because the eligibility checker is shared with the DvP workflow, one run can serve both chains; the artifacts keep separate hashes either way.
Check a synthetic government-bond package through the repo mobility workflow and report the haircut, the eligibility verdict, and the cash-leg finality result.
The capital workflow asks a readiness question and then a sizing question. The Canton Tokenization Readiness Diagnostic scores whether a desk's instruments and processes are ready to tokenize, and the Settlement-Risk Capital Efficiency Optimizer sizes what the settlement-risk footprint becomes once tokenized collateral shortens the settlement cycle.
The chain page is canton-capital-efficiency. Readiness comes first deliberately: an optimizer run over a weak readiness score answers the wrong question.
Score a synthetic desk's tokenization readiness, then size the settlement-risk capital effect of moving its collateral on-chain.
Pick a workflow on the Canton hub, open its tools in order, and let each export feed the next step. When a run finishes, the composite artifact carries every step's execution_hash, which is what makes the whole chain independently re-verifiable.
Other explainers in this series live on the visual explainers hub; the machine-readable chain definitions live in chaingraph.json behind the hub.
Load the canton-repo-mobility workflow via MCP, run its steps in order on synthetic inputs, and return the composite artifact with every parent hash.