[{"data":1,"prerenderedAt":64},["ShallowReactive",2],{"work-platform-modernisation":3},{"id":4,"title":5,"body":6,"client":50,"description":51,"extension":52,"featured":53,"meta":54,"navigation":53,"path":55,"seo":56,"services":57,"stem":61,"year":62,"__hash__":63},"work\u002Fwork\u002Fplatform-modernisation.md","Modernising a business-critical inherited platform without stopping operations",{"type":7,"value":8,"toc":42},"minimark",[9,14,18,22,25,29,32,35,39],[10,11,13],"h2",{"id":12},"context","Context",[15,16,17],"p",{},"The platform had become essential to daily operations while documentation and architectural clarity had not kept pace with its importance.",[10,19,21],{"id":20},"problem","Problem",[15,23,24],{},"A complete rewrite would have introduced unacceptable delivery and operational risk. Continuing without intervention made every future change slower and harder to reason about.",[10,26,28],{"id":27},"approach","Approach",[15,30,31],{},"The engagement begins by reconstructing the actual system: data flows, ownership, dependencies, failure behaviour and operational workarounds.",[15,33,34],{},"Modernisation is then staged around risk rather than fashion.",[10,36,38],{"id":37},"outcome","Outcome",[15,40,41],{},"Use this starter study to document a real rescue or inherited-system engagement once you choose the example you want to publish.",{"title":43,"searchDepth":44,"depth":44,"links":45},"",2,[46,47,48,49],{"id":12,"depth":44,"text":13},{"id":20,"depth":44,"text":21},{"id":27,"depth":44,"text":28},{"id":37,"depth":44,"text":38},"Anonymised platform client","Technical discovery, risk mapping and staged modernisation for a platform that could not simply be rebuilt from scratch.","md",true,{},"\u002Fwork\u002Fplatform-modernisation",{"title":5,"description":51},[58,59,60],"Technical discovery","Legacy modernisation","Architecture","work\u002Fplatform-modernisation",2026,"hbSr7elTrKKHj6tHpezSn_PfDy5Qc0A5HaKUC63gAaE",1787213493731]