Most platform engineering assumes the network is yours to design. In a mine, it isn't. The Purdue model segments corporate, OTSS and OT networks by regulation, and an artefact cannot simply travel from a build runner to a production cluster on the pit floor.
In this talk, Kush Shah covers how FDX, Fortescue's developer platform, deploys across all three layers. He explains why the obvious GitOps answer was the wrong one, where the orchestration model broke at the boundaries, and why some deployments are deliberately still triggered by a human.
Attendees will take away:
How to promote artefacts across segmented networks without abandoning a single golden path
Where standard platform tooling stops working below L4
Why "automate everything" is the wrong goal when the blast radius is a mine