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.
Part of Digital Asset Operations(15)
Buying a Travel Rule tool is not the same as running Travel Rule in production.
The failure mode:
- The tool shows green in demos.
- Hits and misses are not bound to the case.
- Dual control on the transfer cannot see Travel Rule state.
- The evidence pack is a CSV export emailed at month-end.
The production standard, in plain language
Travel Rule outcomes sit in the same evidence trail as the transfer decision. Exceptions have a register. Someone owns the breaks.
What we build
Our Compliance Operations & Evidence and Operator Control Plane foundations, integrated with your Travel Rule provider and ticketing:
- Travel Rule exceptions arrive as cases in a queue with an owner
- Transfer approvals can see screening and Travel Rule state
- Escalation and resolution are recorded
- AI-assisted summaries for investigators, with human decisions
- Evidence generated from the case history
We are not building a competing Travel Rule product, and we give no legal advice on how the rule should be interpreted.
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.
Fence: Implementation only. No keys.