[{"data":1,"prerenderedAt":23},["ShallowReactive",2],{"blog-article-stack-bought-not-wired":3},{"id":4,"slug":5,"body":6,"html":7,"title":8,"description":9,"category":10,"tags":11,"author":15,"date":16,"year":17,"month":18,"quarter":19,"status":20,"featured":21,"series":22,"seriesOrder":18},"2026\u002F08\u002Fdigital-assets\u002Fstack-bought-not-wired","stack-bought-not-wired","Bull markets sell software. Production needs **wiring**.\n\nA familiar failure mode:\n\n- Custody platform live.\n- Travel Rule tool live.\n- KYC live.\n- Tickets live.\n- Dual control not enforced.\n- Travel Rule hits not bound to evidence.\n- Shared admin still smiling in the corner.\n\n## What wiring means\n\nThe missing piece is the **application layer** across those tools, not another tool. In an [AI Production Sprint](\u002Fservices\u002Fai-production-sprint), we configure an operating application on your client-owned stack:\n\n- Policy and dual-control enforcement you can defend\n- The Travel Rule path bound to the case, with the evidence attached\n- A plan to remove shared admin\n- Reconciliation and export jobs\n- Runbooks and handover\n\nRelated workflows then extend through an [Application Family Program](\u002Fservices\u002Fapplication-family-program) on the same identity and integration layer.\n\n## What it is not\n\n- Ripping out and replacing your vendors\n- Hosting keys\n- Competing with your custody provider\n- Open-ended “integration partnering” without a fixed scope\n\n## How it usually starts\n\nAfter a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint), or through a vendor introduction on an account that is stuck. Leading with “we'll re-architect your stack” is usually the wrong opening.\n\nVendors: we build the enterprise workflow layer around your installed technology. See [cloud and technology partners](\u002Fpartners\u002Fcloud-and-technology).\n\n**Next step:** Name the stack and the failure. If you can only name the logo, you are still in procurement theatre.\n\n*Fence: Configure client systems only. No owner keys.*\n","\u003Cp>Bull markets sell software. Production needs \u003Cstrong>wiring\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>A familiar failure mode:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Custody platform live.\u003C\u002Fli>\n\u003Cli>Travel Rule tool live.\u003C\u002Fli>\n\u003Cli>KYC live.\u003C\u002Fli>\n\u003Cli>Tickets live.\u003C\u002Fli>\n\u003Cli>Dual control not enforced.\u003C\u002Fli>\n\u003Cli>Travel Rule hits not bound to evidence.\u003C\u002Fli>\n\u003Cli>Shared admin still smiling in the corner.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What wiring means\u003C\u002Fh2>\n\u003Cp>The missing piece is the \u003Cstrong>application layer\u003C\u002Fstrong> across those tools, not another tool. In an \u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa>, we configure an operating application on your client-owned stack:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Policy and dual-control enforcement you can defend\u003C\u002Fli>\n\u003Cli>The Travel Rule path bound to the case, with the evidence attached\u003C\u002Fli>\n\u003Cli>A plan to remove shared admin\u003C\u002Fli>\n\u003Cli>Reconciliation and export jobs\u003C\u002Fli>\n\u003Cli>Runbooks and handover\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Related workflows then extend through an \u003Ca href=\"\u002Fservices\u002Fapplication-family-program\">Application Family Program\u003C\u002Fa> on the same identity and integration layer.\u003C\u002Fp>\n\u003Ch2>What it is not\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Ripping out and replacing your vendors\u003C\u002Fli>\n\u003Cli>Hosting keys\u003C\u002Fli>\n\u003Cli>Competing with your custody provider\u003C\u002Fli>\n\u003Cli>Open-ended “integration partnering” without a fixed scope\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How it usually starts\u003C\u002Fh2>\n\u003Cp>After a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>, or through a vendor introduction on an account that is stuck. Leading with “we'll re-architect your stack” is usually the wrong opening.\u003C\u002Fp>\n\u003Cp>Vendors: we build the enterprise workflow layer around your installed technology. See \u003Ca href=\"\u002Fpartners\u002Fcloud-and-technology\">cloud and technology partners\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Name the stack and the failure. If you can only name the logo, you are still in procurement theatre.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Configure client systems only. No owner keys.\u003C\u002Fem>\u003C\u002Fp>\n","Stack bought, not wired","Custody, Travel Rule, and KYC can all be live while dual control and evidence remain unwired. Integration work closes that gap.","digital-assets",[12,13,14,10],"integration","implementation","operations","xzero-media-editorial","2026-08-29T00:00:00.000Z",2026,8,3,"published",false,"digital-asset-operations",1791555299222]