[{"data":1,"prerenderedAt":61},["ShallowReactive",2],{"insight-storefront-boundary":3},{"id":4,"title":5,"body":6,"category":51,"date":52,"description":53,"extension":54,"meta":55,"navigation":56,"path":57,"seo":58,"stem":59,"__hash__":60},"insights\u002Finsights\u002Fstorefront-boundary.md","Why commerce architecture stops at the wrong boundary",{"type":7,"value":8,"toc":46},"minimark",[9,13,16,35,40,43],[10,11,12],"p",{},"A storefront is easy to draw on an architecture diagram because its boundary is visually obvious. Operational commerce is not.",[10,14,15],{},"The difficult questions often begin after a customer has already paid:",[17,18,19,23,26,29,32],"ul",{},[20,21,22],"li",{},"Which system owns the order now?",[20,24,25],{},"Which inventory state is authoritative?",[20,27,28],{},"What happens when fulfilment can only be partially completed?",[20,30,31],{},"Who can safely retry a failed integration?",[20,33,34],{},"Which system is allowed to print the shipping artefact?",[36,37,39],"h2",{"id":38},"architecture-should-follow-responsibility","Architecture should follow responsibility",[10,41,42],{},"A useful architecture map does not merely show APIs. It shows who owns decisions and state.",[10,44,45],{},"That distinction is what turns a collection of integrations into an operable system.",{"title":47,"searchDepth":48,"depth":48,"links":49},"",2,[50],{"id":38,"depth":48,"text":39},"Commerce Architecture","2026-08-14","The storefront is visible, but the expensive failures often happen after checkout.","md",{},true,"\u002Finsights\u002Fstorefront-boundary",{"title":5,"description":53},"insights\u002Fstorefront-boundary","minPigi9A4w8Ufsz8fIPwCvYkLA110gkUEp6SAcyLOo",1787213493756]