[{"data":1,"prerenderedAt":24},["ShallowReactive",2],{"blog-article-travel-rule-without-the-evidence-plane":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":23},"2026\u002F09\u002Fdigital-assets\u002Ftravel-rule-without-the-evidence-plane","travel-rule-without-the-evidence-plane","Buying a Travel Rule tool is not the same as running Travel Rule in production.\n\nThe failure mode:\n\n- The tool shows green in demos.\n- Hits and misses are not bound to the case.\n- Dual control on the transfer cannot see Travel Rule state.\n- The evidence pack is a CSV export emailed at month-end.\n\n## The production standard, in plain language\n\nTravel Rule outcomes sit in the **same evidence trail** as the transfer decision.\nExceptions have a register.\nSomeone owns the breaks.\n\n## What we build\n\nOur [Compliance Operations & Evidence](\u002Findustries\u002Fdigital-assets) and Operator Control Plane foundations, integrated with your Travel Rule provider and ticketing:\n\n- Travel Rule exceptions arrive as cases in a queue with an owner\n- Transfer approvals can see screening and Travel Rule state\n- Escalation and resolution are recorded\n- AI-assisted summaries for investigators, with human decisions\n- Evidence generated from the case history\n\nWe are not building a competing Travel Rule product, and we give no legal advice on how the rule should be interpreted.\n\n**Next step:** Ask for last week's transfer where Travel Rule, dual control and case evidence form one path. If that takes a day to assemble, you have found the workflow to [bring us](\u002Fcontact).\n\n*Fence: Implementation only. No keys.*\n","\u003Cp>Buying a Travel Rule tool is not the same as running Travel Rule in production.\u003C\u002Fp>\n\u003Cp>The failure mode:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The tool shows green in demos.\u003C\u002Fli>\n\u003Cli>Hits and misses are not bound to the case.\u003C\u002Fli>\n\u003Cli>Dual control on the transfer cannot see Travel Rule state.\u003C\u002Fli>\n\u003Cli>The evidence pack is a CSV export emailed at month-end.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>The production standard, in plain language\u003C\u002Fh2>\n\u003Cp>Travel Rule outcomes sit in the \u003Cstrong>same evidence trail\u003C\u002Fstrong> as the transfer decision.\nExceptions have a register.\nSomeone owns the breaks.\u003C\u002Fp>\n\u003Ch2>What we build\u003C\u002Fh2>\n\u003Cp>Our \u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Compliance Operations & Evidence\u003C\u002Fa> and Operator Control Plane foundations, integrated with your Travel Rule provider and ticketing:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Travel Rule exceptions arrive as cases in a queue with an owner\u003C\u002Fli>\n\u003Cli>Transfer approvals can see screening and Travel Rule state\u003C\u002Fli>\n\u003Cli>Escalation and resolution are recorded\u003C\u002Fli>\n\u003Cli>AI-assisted summaries for investigators, with human decisions\u003C\u002Fli>\n\u003Cli>Evidence generated from the case history\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>We are not building a competing Travel Rule product, and we give no legal advice on how the rule should be interpreted.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Ask for last week's transfer where Travel Rule, dual control and case evidence form one path. If that takes a day to assemble, you have found the workflow to \u003Ca href=\"\u002Fcontact\">bring us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Implementation only. No keys.\u003C\u002Fem>\u003C\u002Fp>\n","Travel Rule without the evidence plane","A Travel Rule tool that does not bind hits to the ticket is not production. Outcomes must sit on the same evidence plane.","digital-assets",[12,13,14,10],"compliance","aml","operations","xzero-media-editorial","2026-09-05T00:00:00.000Z",2026,9,3,"published",false,"digital-asset-operations",15,1791555299579]