Journeys › sched-001
Carbon-aware federated placement
A submitted workload is placed on the lowest-carbon node that every permission, jurisdiction and capacity rule allows, across CPUs, GPUs, clouds and on-premises machines, with a signed receipt.
Sender Blue squad engineer (junior IT team)Receiver Blue squad lead reading the placementRegulation REG-GSF-SCI, REG-EED-12, REG-NESO
- Read the live UK grid carbon from carbon.judiverse.tech
- Submit a GPU training workload with residency 'any'
- Scheduler places it and issues a receipt
- Check no lawful node had lower carbon
Receiving side: the squad lead opens the workload and sees its node, carbon per hour and receipt. Failure path: Submit a workload with an unknown classification → refused with the reason and a receipt; no workload is created.