[{"data":1,"prerenderedAt":202},["ShallowReactive",2],{"blog-series-digital-asset-operations":3},[4,25,37,47,57,68,78,88,98,108,118,128,138,148,158,169,182,192],{"id":5,"slug":6,"body":7,"html":8,"title":9,"description":10,"category":11,"tags":12,"author":16,"date":17,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":24},"2026\u002F08\u002Fdigital-assets\u002Flicence-is-not-production","licence-is-not-production","The certificate on the wall is not an operating model.\n\nA VARA (or equivalent) licence answers a different question than production does. The licence says you are allowed to run certain activities. Production asks whether **onboarding → first transfer** (or the one workflow that actually makes money) runs with dual control, real evidence, and owners who can show the path without digging through email.\n\nThe same pattern shows up again and again:\n\n- The licence is live.\n- The stack is partly bought (custody, Travel Rule, KYC, tickets).\n- The book still lives in sheets, chat and “the person who knows.”\n- Dual control exists in a policy PDF and dies on Tuesday afternoon.\n\nThat gap is not a strategy problem. It is a **production** problem.\n\n## What “production” means here\n\nFor one named workflow:\n\n1. **As-is** is written down: people, systems, tickets, and where proof actually lives.\n2. **To-be** is operable: dual control, gates and exceptions, not a vision deck.\n3. **Evidence** is produced by the workflow itself, not assembled from screenshots after the fact.\n4. **The path to production** has owners inside the firm, not a consultant forever.\n\nIf you cannot name the workflow, you are not ready to buy anything. You are still in narrative mode.\n\n## What we build\n\nThe operating model goes into an **application**, not a folder. We start from a deployment-ready foundation (operator control plane, compliance operations and evidence, custody operations, stablecoin settlement) and configure it to your stack:\n\n- A [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint) defines the workflow, controls, evidence and the delta.\n- An [AI Production Sprint](\u002Fservices\u002Fai-production-sprint) configures and integrates the application.\n\n## What we do not sell\n\n- Keys or custody\n- Licence filing\n- Virtual-asset advisory\n- A promise that an exam will pass\n\nImplementation services under a mainland DLT \u002F cloud licence. **Not a VASP.**\n\n**Next step:** If the licensed entity and one workflow are nameable, [bring us the workflow](\u002Fcontact).\n\n*Fence: No custody, no keys, no licence filing, no VA advisory.*\n","\u003Cp>The certificate on the wall is not an operating model.\u003C\u002Fp>\n\u003Cp>A VARA (or equivalent) licence answers a different question than production does. The licence says you are allowed to run certain activities. Production asks whether \u003Cstrong>onboarding → first transfer\u003C\u002Fstrong> (or the one workflow that actually makes money) runs with dual control, real evidence, and owners who can show the path without digging through email.\u003C\u002Fp>\n\u003Cp>The same pattern shows up again and again:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The licence is live.\u003C\u002Fli>\n\u003Cli>The stack is partly bought (custody, Travel Rule, KYC, tickets).\u003C\u002Fli>\n\u003Cli>The book still lives in sheets, chat and “the person who knows.”\u003C\u002Fli>\n\u003Cli>Dual control exists in a policy PDF and dies on Tuesday afternoon.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>That gap is not a strategy problem. It is a \u003Cstrong>production\u003C\u002Fstrong> problem.\u003C\u002Fp>\n\u003Ch2>What “production” means here\u003C\u002Fh2>\n\u003Cp>For one named workflow:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>As-is\u003C\u002Fstrong> is written down: people, systems, tickets, and where proof actually lives.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>To-be\u003C\u002Fstrong> is operable: dual control, gates and exceptions, not a vision deck.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Evidence\u003C\u002Fstrong> is produced by the workflow itself, not assembled from screenshots after the fact.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The path to production\u003C\u002Fstrong> has owners inside the firm, not a consultant forever.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you cannot name the workflow, you are not ready to buy anything. You are still in narrative mode.\u003C\u002Fp>\n\u003Ch2>What we build\u003C\u002Fh2>\n\u003Cp>The operating model goes into an \u003Cstrong>application\u003C\u002Fstrong>, not a folder. We start from a deployment-ready foundation (operator control plane, compliance operations and evidence, custody operations, stablecoin settlement) and configure it to your stack:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa> defines the workflow, controls, evidence and the delta.\u003C\u002Fli>\n\u003Cli>An \u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa> configures and integrates the application.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What we do not sell\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Keys or custody\u003C\u002Fli>\n\u003Cli>Licence filing\u003C\u002Fli>\n\u003Cli>Virtual-asset advisory\u003C\u002Fli>\n\u003Cli>A promise that an exam will pass\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Implementation services under a mainland DLT \u002F cloud licence. \u003Cstrong>Not a VASP.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If the licensed entity and one workflow are nameable, \u003Ca href=\"\u002Fcontact\">bring us the workflow\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: No custody, no keys, no licence filing, no VA advisory.\u003C\u002Fem>\u003C\u002Fp>\n","Licence is not production","A licence says you may operate. Production asks whether one named workflow actually runs with dual control and evidence.","digital-assets",[13,14,15,11],"licensing","operations","governance","fazezero-editorial","2026-08-22T00:00:00.000Z",2026,8,3,"published",false,"digital-asset-operations",1,{"id":26,"slug":27,"body":28,"html":29,"title":30,"description":31,"category":11,"tags":32,"author":16,"date":35,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":36},"2026\u002F08\u002Fdigital-assets\u002Fone-workflow-not-a-transformation","one-workflow-not-a-transformation","Transformation programmes are how regulated teams postpone production.\n\nThey sound responsible: multi-workstream, multi-vendor, multi-quarter. They also guarantee that dual control on the *money* workflow stays unfinished while the workshops multiply.\n\nOur engagements are narrow on purpose.\n\n## The rule\n\n**One named workflow per engagement.**\nThe usual default is onboarding → first transfer, or the first settlement event that creates real risk.\n\nA second workflow is a **change request**, not a favour.\n\n## Why buyers accept this\n\n- Scope is fixed and deliverables are clear.\n- The outcome is a decision: build it, or don't.\n- Controls and evidence are proven on one path before you industrialise everything.\n\n## Why this is easier for us than for most\n\nWe don't start from a blank repository. The workflow is mapped onto an existing application foundation built on the same architecture as everything else we deliver. A narrow first scope is cheap to extend later through an [Application Family Program](\u002Fservices\u002Fapplication-family-program), because the identity, integrations and evidence model are shared.\n\n## How it shows up\n\n- A [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint) defines production for *this* book: as-is, to-be, controls, evidence and the delta.\n- An [AI Production Sprint](\u002Fservices\u002Fai-production-sprint) configures and integrates the application on *your* systems.\n\nIf a vendor cannot describe deliverables for **one** workflow without inventing a programme office, they are not selling production.\n\n**Next step:** [Bring the workflow name](\u002Fcontact). If you cannot name it, don't buy yet.\n\n*Fence: Implementation only. Not a VASP.*\n","\u003Cp>Transformation programmes are how regulated teams postpone production.\u003C\u002Fp>\n\u003Cp>They sound responsible: multi-workstream, multi-vendor, multi-quarter. They also guarantee that dual control on the \u003Cem>money\u003C\u002Fem> workflow stays unfinished while the workshops multiply.\u003C\u002Fp>\n\u003Cp>Our engagements are narrow on purpose.\u003C\u002Fp>\n\u003Ch2>The rule\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>One named workflow per engagement.\u003C\u002Fstrong>\nThe usual default is onboarding → first transfer, or the first settlement event that creates real risk.\u003C\u002Fp>\n\u003Cp>A second workflow is a \u003Cstrong>change request\u003C\u002Fstrong>, not a favour.\u003C\u002Fp>\n\u003Ch2>Why buyers accept this\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Scope is fixed and deliverables are clear.\u003C\u002Fli>\n\u003Cli>The outcome is a decision: build it, or don't.\u003C\u002Fli>\n\u003Cli>Controls and evidence are proven on one path before you industrialise everything.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Why this is easier for us than for most\u003C\u002Fh2>\n\u003Cp>We don't start from a blank repository. The workflow is mapped onto an existing application foundation built on the same architecture as everything else we deliver. A narrow first scope is cheap to extend later through an \u003Ca href=\"\u002Fservices\u002Fapplication-family-program\">Application Family Program\u003C\u002Fa>, because the identity, integrations and evidence model are shared.\u003C\u002Fp>\n\u003Ch2>How it shows up\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa> defines production for \u003Cem>this\u003C\u002Fem> book: as-is, to-be, controls, evidence and the delta.\u003C\u002Fli>\n\u003Cli>An \u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa> configures and integrates the application on \u003Cem>your\u003C\u002Fem> systems.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If a vendor cannot describe deliverables for \u003Cstrong>one\u003C\u002Fstrong> workflow without inventing a programme office, they are not selling production.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> \u003Ca href=\"\u002Fcontact\">Bring the workflow name\u003C\u002Fa>. If you cannot name it, don't buy yet.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Implementation only. Not a VASP.\u003C\u002Fem>\u003C\u002Fp>\n","One workflow, not a transformation","Public offers stay narrow: one named workflow per statement of work, not a multi-quarter transformation programme.",[14,33,34,11],"implementation","enterprise","2026-08-23T00:00:00.000Z",2,{"id":38,"slug":39,"body":40,"html":41,"title":42,"description":43,"category":11,"tags":44,"author":16,"date":46,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":20},"2026\u002F08\u002Fdigital-assets\u002Fdual-control-that-survives-tuesday","dual-control-that-survives-tuesday","Most “dual control” is a slide.\n\nIt dies when:\n\n- Shared admin is still on.\n- The maker and checker are the same person after hours.\n- The tool allows a bypass that nobody logs.\n- The ticket closed without the evidence attached.\n\nTuesday is the test. Volume is up. Someone is on leave. The corridor is busy. Policy PDFs do not move.\n\n## Production dual control has four parts\n\n1. **Policy that the system enforces**, or a manual gate that is actually staffed.\n2. **Segregation that survives staffing gaps**: named roles, not heroics.\n3. **An exception path** with a register, not a private chat.\n4. **Evidence** that the dual-control event happened, linked to the work item.\n\nIf any one of those is missing, you have theatre.\n\n## Where it should live\n\nIn an application, not a procedure document. Maker\u002Fchecker, approval routing, the exception register and evidence capture belong in the operating layer that sits across your custody, screening and ticketing tools. That is what our [Virtual Asset Operator Control Plane](\u002Findustries\u002Fdigital-assets) foundation is built for.\n\nWe do not sell a new custody product and we never hold keys. A [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint) maps where dual control fails today for one workflow. An [AI Production Sprint](\u002Fservices\u002Fai-production-sprint) configures the application on the stack you already run.\n\n## Red flags in a first conversation\n\n- “We have dual control,” but nobody can show last week’s maker\u002Fchecker record.\n- Owner keys discussed as something we would hold. We will not.\n- A request to “make the tool compliant” without naming the workflow.\n\n[Digital asset applications](\u002Findustries\u002Fdigital-assets) · [How we work](\u002Fcompany\u002Fhow-we-work)\n\n**Next step:** If dual control fails on a real book this month, [bring us the workflow](\u002Fcontact). That is a production problem, not a branding problem.\n\n*Fence: We build and integrate applications on client-owned systems. No owner or root admin. No keys.*\n","\u003Cp>Most “dual control” is a slide.\u003C\u002Fp>\n\u003Cp>It dies when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Shared admin is still on.\u003C\u002Fli>\n\u003Cli>The maker and checker are the same person after hours.\u003C\u002Fli>\n\u003Cli>The tool allows a bypass that nobody logs.\u003C\u002Fli>\n\u003Cli>The ticket closed without the evidence attached.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Tuesday is the test. Volume is up. Someone is on leave. The corridor is busy. Policy PDFs do not move.\u003C\u002Fp>\n\u003Ch2>Production dual control has four parts\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Policy that the system enforces\u003C\u002Fstrong>, or a manual gate that is actually staffed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Segregation that survives staffing gaps\u003C\u002Fstrong>: named roles, not heroics.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>An exception path\u003C\u002Fstrong> with a register, not a private chat.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Evidence\u003C\u002Fstrong> that the dual-control event happened, linked to the work item.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If any one of those is missing, you have theatre.\u003C\u002Fp>\n\u003Ch2>Where it should live\u003C\u002Fh2>\n\u003Cp>In an application, not a procedure document. Maker\u002Fchecker, approval routing, the exception register and evidence capture belong in the operating layer that sits across your custody, screening and ticketing tools. That is what our \u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Virtual Asset Operator Control Plane\u003C\u002Fa> foundation is built for.\u003C\u002Fp>\n\u003Cp>We do not sell a new custody product and we never hold keys. A \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa> maps where dual control fails today for one workflow. An \u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa> configures the application on the stack you already run.\u003C\u002Fp>\n\u003Ch2>Red flags in a first conversation\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>“We have dual control,” but nobody can show last week’s maker\u002Fchecker record.\u003C\u002Fli>\n\u003Cli>Owner keys discussed as something we would hold. We will not.\u003C\u002Fli>\n\u003Cli>A request to “make the tool compliant” without naming the workflow.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Digital asset applications\u003C\u002Fa> · \u003Ca href=\"\u002Fcompany\u002Fhow-we-work\">How we work\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If dual control fails on a real book this month, \u003Ca href=\"\u002Fcontact\">bring us the workflow\u003C\u002Fa>. That is a production problem, not a branding problem.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: We build and integrate applications on client-owned systems. No owner or root admin. No keys.\u003C\u002Fem>\u003C\u002Fp>\n","Dual control that survives Tuesday","Dual control that only exists in a policy PDF fails on a busy Tuesday. Production dual control is enforced, staffed, and evidenced.",[15,14,45,11],"compliance","2026-08-24T00:00:00.000Z",{"id":48,"slug":49,"body":50,"html":51,"title":52,"description":53,"category":11,"tags":54,"author":16,"date":55,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":56},"2026\u002F08\u002Fdigital-assets\u002Fticket-equals-evidence","ticket-equals-evidence","Examiners do not want your mythology. They want a path from **decision → actor → artefact**.\n\nIf proof lives in:\n\n- personal email,\n- chat exports,\n- desktop folders,\n- or “we can rebuild it if asked,”\n\nyou do not have evidence. You have archaeology.\n\n## The production rule\n\n**The work item (a case, ticket or equivalent) is the primary key for evidence.**\n\nScreenshots may be attached. They do not replace the key.\n\nExports and reports should be reproducible from the same model, not handmade the night before a mock exam.\n\n## Evidence belongs in the application\n\nOur [Compliance Operations & Evidence](\u002Findustries\u002Fdigital-assets) foundations treat evidence as a feature:\n\n- Audit events on every decision and approval\n- Control-to-evidence mapping\n- An exception register linked to the case\n- Retention and export shapes a CCO can defend\n- AI-assisted evidence-pack generation, reviewed by a human\n\n## Exam pressure\n\nIf a mock or exam is close, **Exam & Evidence Readiness** is available alongside an application engagement. It covers the pack structure, the gaps and a dry run. There is still no pass promise and no regulator liaison.\n\n[Digital asset applications and add-ons](\u002Findustries\u002Fdigital-assets)\n\n**Next step:** Ask internally: “Show me last week's first transfer with dual control and evidence in one path.” If the room goes quiet, you know what to [bring us](\u002Fcontact).\n\n*Fence: Evidence implementation on client systems. We do not speak to the regulator for you.*\n","\u003Cp>Examiners do not want your mythology. They want a path from \u003Cstrong>decision → actor → artefact\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>If proof lives in:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>personal email,\u003C\u002Fli>\n\u003Cli>chat exports,\u003C\u002Fli>\n\u003Cli>desktop folders,\u003C\u002Fli>\n\u003Cli>or “we can rebuild it if asked,”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>you do not have evidence. You have archaeology.\u003C\u002Fp>\n\u003Ch2>The production rule\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>The work item (a case, ticket or equivalent) is the primary key for evidence.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Screenshots may be attached. They do not replace the key.\u003C\u002Fp>\n\u003Cp>Exports and reports should be reproducible from the same model, not handmade the night before a mock exam.\u003C\u002Fp>\n\u003Ch2>Evidence belongs in the application\u003C\u002Fh2>\n\u003Cp>Our \u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Compliance Operations & Evidence\u003C\u002Fa> foundations treat evidence as a feature:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Audit events on every decision and approval\u003C\u002Fli>\n\u003Cli>Control-to-evidence mapping\u003C\u002Fli>\n\u003Cli>An exception register linked to the case\u003C\u002Fli>\n\u003Cli>Retention and export shapes a CCO can defend\u003C\u002Fli>\n\u003Cli>AI-assisted evidence-pack generation, reviewed by a human\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Exam pressure\u003C\u002Fh2>\n\u003Cp>If a mock or exam is close, \u003Cstrong>Exam & Evidence Readiness\u003C\u002Fstrong> is available alongside an application engagement. It covers the pack structure, the gaps and a dry run. There is still no pass promise and no regulator liaison.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Digital asset applications and add-ons\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Ask internally: “Show me last week's first transfer with dual control and evidence in one path.” If the room goes quiet, you know what to \u003Ca href=\"\u002Fcontact\">bring us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Evidence implementation on client systems. We do not speak to the regulator for you.\u003C\u002Fem>\u003C\u002Fp>\n","Ticket = evidence","Examiners want a path from decision to actor to artefact. The ticket is the primary key for evidence, not a folder of screenshots.",[45,15,14,11],"2026-08-25T00:00:00.000Z",4,{"id":58,"slug":59,"body":60,"html":61,"title":62,"description":63,"category":11,"tags":64,"author":16,"date":66,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":67},"2026\u002F08\u002Fdigital-assets\u002Fwhen-the-calendar-is-the-enemy","when-the-calendar-is-the-enemy","Some problems are design problems. Some are **calendar** problems.\n\nIf a mock or exam is close, a long architecture exercise may be the wrong first move. You need a pack structure, a gap burn-down and a dry run, fast, without pretending anyone can guarantee a pass.\n\n## Exam & Evidence Readiness\n\nIt is available **alongside an application engagement**, for one workflow:\n\n- Where evidence lives today\n- Control-to-evidence mapping\n- Pack layout by the question themes you actually face\n- Critical gaps, with owners and dates\n- An exception register structure\n- A dry-run checklist\n\n## Why we pair it with the application\n\nA pack assembled by hand gets rebuilt by hand for the next exam. The durable fix is an application that produces the evidence as the work happens: our Compliance Operations & Evidence and Operator Control Plane foundations. Readiness buys you the next date. The application buys you every date after that.\n\n## What it is not\n\n- A pass promise\n- Counsel or regulator representation\n- A rewrite of your entire policy suite\n\n## Commercial reality\n\nA deposit to start, and a named owner on your side. If the date is days away and nothing can change in time, we'll tell you plainly.\n\n[Digital asset applications and add-ons](\u002Findustries\u002Fdigital-assets)\n\n**Next step:** Put the exam or mock date in [your first message](\u002Fcontact).\n\n*Fence: No guarantee of exam outcome. No regulator liaison.*\n","\u003Cp>Some problems are design problems. Some are \u003Cstrong>calendar\u003C\u002Fstrong> problems.\u003C\u002Fp>\n\u003Cp>If a mock or exam is close, a long architecture exercise may be the wrong first move. You need a pack structure, a gap burn-down and a dry run, fast, without pretending anyone can guarantee a pass.\u003C\u002Fp>\n\u003Ch2>Exam & Evidence Readiness\u003C\u002Fh2>\n\u003Cp>It is available \u003Cstrong>alongside an application engagement\u003C\u002Fstrong>, for one workflow:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Where evidence lives today\u003C\u002Fli>\n\u003Cli>Control-to-evidence mapping\u003C\u002Fli>\n\u003Cli>Pack layout by the question themes you actually face\u003C\u002Fli>\n\u003Cli>Critical gaps, with owners and dates\u003C\u002Fli>\n\u003Cli>An exception register structure\u003C\u002Fli>\n\u003Cli>A dry-run checklist\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Why we pair it with the application\u003C\u002Fh2>\n\u003Cp>A pack assembled by hand gets rebuilt by hand for the next exam. The durable fix is an application that produces the evidence as the work happens: our Compliance Operations & Evidence and Operator Control Plane foundations. Readiness buys you the next date. The application buys you every date after that.\u003C\u002Fp>\n\u003Ch2>What it is not\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A pass promise\u003C\u002Fli>\n\u003Cli>Counsel or regulator representation\u003C\u002Fli>\n\u003Cli>A rewrite of your entire policy suite\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Commercial reality\u003C\u002Fh2>\n\u003Cp>A deposit to start, and a named owner on your side. If the date is days away and nothing can change in time, we'll tell you plainly.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Digital asset applications and add-ons\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Put the exam or mock date in \u003Ca href=\"\u002Fcontact\">your first message\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: No guarantee of exam outcome. No regulator liaison.\u003C\u002Fem>\u003C\u002Fp>\n","When the calendar is the enemy","When a mock or exam is close, evidence readiness has to run alongside the fix. Why we pair it with application work and never promise a pass.",[45,65,14,11],"regulation","2026-08-26T00:00:00.000Z",5,{"id":69,"slug":70,"body":71,"html":72,"title":73,"description":74,"category":11,"tags":75,"author":16,"date":76,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":77},"2026\u002F08\u002Fdigital-assets\u002Fwhat-you-get-in-three-weeks","what-you-get-in-three-weeks","If the output is only slides, you bought theatre.\n\nFor digital-asset operators, a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint) ends with a scope a decision-maker can act on, mapped onto an existing application foundation.\n\n## What you get (typical)\n\n1. Problem definition, sponsor and RACI for one workflow\n2. As-is map: people, systems, tickets and evidence gaps\n3. To-be workflow: dual control, gates and exceptions\n4. Business requirements, use cases and user stories\n5. Domain model, bounded contexts and the integration inventory (custody, KYC\u002FKYT, Travel Rule, ticketing, banking rails)\n6. Control and evidence requirements mapped to that workflow\n7. Target architecture and API requirements\n8. The closest application foundation, and the **customer-specific delta**\n9. Implementation scope and a production path\n\n## What “done” means\n\n- The named workflow has a clear to-be.\n- The CCO can point to the control and evidence model.\n- The build decision is made, or explicitly deferred, with owners.\n\nIt does not mean “we aligned stakeholders,” and it does not mean “platform roadmap.”\n\n## After the sprint\n\n- [AI Production Sprint](\u002Fservices\u002Fai-production-sprint): configure and integrate the application.\n- [Application Family Program](\u002Fservices\u002Fapplication-family-program): extend to related workflows.\n- Add-ons: Exam & Evidence Readiness, Operator Enablement Lab, Fractional Production Owner.\n\nNone of those are forced.\n\n**Next step:** [Bring us the workflow](\u002Fcontact). If the shape above is wrong for you, we'll say so.\n\n*Fence: Application engineering. Not custody. Not legal advice.*\n","\u003Cp>If the output is only slides, you bought theatre.\u003C\u002Fp>\n\u003Cp>For digital-asset operators, a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa> ends with a scope a decision-maker can act on, mapped onto an existing application foundation.\u003C\u002Fp>\n\u003Ch2>What you get (typical)\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Problem definition, sponsor and RACI for one workflow\u003C\u002Fli>\n\u003Cli>As-is map: people, systems, tickets and evidence gaps\u003C\u002Fli>\n\u003Cli>To-be workflow: dual control, gates and exceptions\u003C\u002Fli>\n\u003Cli>Business requirements, use cases and user stories\u003C\u002Fli>\n\u003Cli>Domain model, bounded contexts and the integration inventory (custody, KYC\u002FKYT, Travel Rule, ticketing, banking rails)\u003C\u002Fli>\n\u003Cli>Control and evidence requirements mapped to that workflow\u003C\u002Fli>\n\u003Cli>Target architecture and API requirements\u003C\u002Fli>\n\u003Cli>The closest application foundation, and the \u003Cstrong>customer-specific delta\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Implementation scope and a production path\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>What “done” means\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>The named workflow has a clear to-be.\u003C\u002Fli>\n\u003Cli>The CCO can point to the control and evidence model.\u003C\u002Fli>\n\u003Cli>The build decision is made, or explicitly deferred, with owners.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It does not mean “we aligned stakeholders,” and it does not mean “platform roadmap.”\u003C\u002Fp>\n\u003Ch2>After the sprint\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa>: configure and integrate the application.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fservices\u002Fapplication-family-program\">Application Family Program\u003C\u002Fa>: extend to related workflows.\u003C\u002Fli>\n\u003Cli>Add-ons: Exam & Evidence Readiness, Operator Enablement Lab, Fractional Production Owner.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>None of those are forced.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> \u003Ca href=\"\u002Fcontact\">Bring us the workflow\u003C\u002Fa>. If the shape above is wrong for you, we'll say so.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Application engineering. Not custody. Not legal advice.\u003C\u002Fem>\u003C\u002Fp>\n","What a Solution Definition Sprint leaves on the table","A Solution Definition Sprint ends with a buildable scope for one workflow, mapped to an existing application foundation. Not slides.",[33,14,34,11],"2026-08-27T00:00:00.000Z",6,{"id":79,"slug":80,"body":81,"html":82,"title":83,"description":84,"category":11,"tags":85,"author":16,"date":86,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":87},"2026\u002F08\u002Fdigital-assets\u002Foperator-lab-after-the-sprint","operator-lab-after-the-sprint","Hiring is slow. Volume is not.\n\nThe **Operator Enablement Lab** is not a public “crypto course.” It is practice on the application and operating workflow your team actually runs: maker\u002Fchecker, exceptions, escalation and evidence.\n\n## The rule we enforce\n\n**After the application is implemented.**\nOtherwise you are training people on fog.\n\n## Format\n\n- One or two days, closed to your firm\n- Scenario-based drills inside the implemented application\n- Maker\u002Fchecker scenarios, exception handling, evidence generation and escalation\n\nWhere it makes sense, we deliver it with training partners.\n\n## What success looks like\n\nOperators can run the path without a consultant in the chair.\nThe CCO still owns accountability. We never take keys, and training does not turn us into your shadow operations team.\n\n[Digital asset applications and add-ons](\u002Findustries\u002Fdigital-assets)\n\n**Next step:** If the application is live and the team cannot run it confidently, the Lab is the right buy. Another strategy offsite is not.\n\n*Fence: Training on production operations and evidence. Not licensing education. Not advice on buying or selling assets.*\n","\u003Cp>Hiring is slow. Volume is not.\u003C\u002Fp>\n\u003Cp>The \u003Cstrong>Operator Enablement Lab\u003C\u002Fstrong> is not a public “crypto course.” It is practice on the application and operating workflow your team actually runs: maker\u002Fchecker, exceptions, escalation and evidence.\u003C\u002Fp>\n\u003Ch2>The rule we enforce\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>After the application is implemented.\u003C\u002Fstrong>\nOtherwise you are training people on fog.\u003C\u002Fp>\n\u003Ch2>Format\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>One or two days, closed to your firm\u003C\u002Fli>\n\u003Cli>Scenario-based drills inside the implemented application\u003C\u002Fli>\n\u003Cli>Maker\u002Fchecker scenarios, exception handling, evidence generation and escalation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Where it makes sense, we deliver it with training partners.\u003C\u002Fp>\n\u003Ch2>What success looks like\u003C\u002Fh2>\n\u003Cp>Operators can run the path without a consultant in the chair.\nThe CCO still owns accountability. We never take keys, and training does not turn us into your shadow operations team.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Digital asset applications and add-ons\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If the application is live and the team cannot run it confidently, the Lab is the right buy. Another strategy offsite is not.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Training on production operations and evidence. Not licensing education. Not advice on buying or selling assets.\u003C\u002Fem>\u003C\u002Fp>\n","Operator enablement comes after the application","Operator Enablement Lab is scenario practice on the implemented application, sold after delivery, not a standalone crypto course.",[14,33,15,11],"2026-08-28T00:00:00.000Z",7,{"id":89,"slug":90,"body":91,"html":92,"title":93,"description":94,"category":11,"tags":95,"author":16,"date":97,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":19},"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.",[96,33,14,11],"integration","2026-08-29T00:00:00.000Z",{"id":99,"slug":100,"body":101,"html":102,"title":103,"description":104,"category":11,"tags":105,"author":16,"date":106,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":107},"2026\u002F08\u002Fdigital-assets\u002Fyou-licence-we-productionize","you-licence-we-productionize","Law firms get clients authorised. Then the client discovers that **licence ≠ production**.\n\nThat failure is not a legal drafting problem. It is dual control, evidence, day-one operations, and a book that still runs on sheets.\n\n## A clean fence (why counsel can refer us)\n\n**Counsel** owns the licence, the legal work and regulatory representation: applications and opinions.\n\n**fazeZERO** owns the operating applications: the [operator control plane, compliance operations and evidence, custody operations and settlement workflows](\u002Findustries\u002Fdigital-assets), configured to the client's stack. We also offer Exam & Evidence Readiness alongside that work. Pre-licence operational design happens only as a counsel-led engagement.\n\nWe do **not** file licences, give VA advisory or hold keys.\nYou do **not** need us competing as fake counsel.\n\n## The ask\n\nOne warm introduction to a CCO or COO at a licensed or newly licensed operator.\nWhen we see a pure licence need, we send it your way.\n\nSwap one-pagers. One intro each way in seven days beats a partnership MoU that never moves.\n\n[Partners](\u002Fpartners) · [How we work](\u002Fcompany\u002Fhow-we-work)\n\n**Next step:** Counsel: [tell us](\u002Fcontact) your preferred intro format. Operators: ask your counsel whether day-one production is staffed.\n\n*Fence: Referral is intro-only. No legal work by fazeZERO.*\n","\u003Cp>Law firms get clients authorised. Then the client discovers that \u003Cstrong>licence ≠ production\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>That failure is not a legal drafting problem. It is dual control, evidence, day-one operations, and a book that still runs on sheets.\u003C\u002Fp>\n\u003Ch2>A clean fence (why counsel can refer us)\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Counsel\u003C\u002Fstrong> owns the licence, the legal work and regulatory representation: applications and opinions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>fazeZERO\u003C\u002Fstrong> owns the operating applications: the \u003Ca href=\"\u002Findustries\u002Fdigital-assets\">operator control plane, compliance operations and evidence, custody operations and settlement workflows\u003C\u002Fa>, configured to the client's stack. We also offer Exam & Evidence Readiness alongside that work. Pre-licence operational design happens only as a counsel-led engagement.\u003C\u002Fp>\n\u003Cp>We do \u003Cstrong>not\u003C\u002Fstrong> file licences, give VA advisory or hold keys.\nYou do \u003Cstrong>not\u003C\u002Fstrong> need us competing as fake counsel.\u003C\u002Fp>\n\u003Ch2>The ask\u003C\u002Fh2>\n\u003Cp>One warm introduction to a CCO or COO at a licensed or newly licensed operator.\nWhen we see a pure licence need, we send it your way.\u003C\u002Fp>\n\u003Cp>Swap one-pagers. One intro each way in seven days beats a partnership MoU that never moves.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Fpartners\">Partners\u003C\u002Fa> · \u003Ca href=\"\u002Fcompany\u002Fhow-we-work\">How we work\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Counsel: \u003Ca href=\"\u002Fcontact\">tell us\u003C\u002Fa> your preferred intro format. Operators: ask your counsel whether day-one production is staffed.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Referral is intro-only. No legal work by fazeZERO.\u003C\u002Fem>\u003C\u002Fp>\n","You licence. We productionize.","Counsel gets the licence. We productionize day-one operations: dual control, evidence, and a book that does not still run on sheets.",[13,14,15,11],"2026-08-30T00:00:00.000Z",9,{"id":109,"slug":110,"body":111,"html":112,"title":113,"description":114,"category":11,"tags":115,"author":16,"date":116,"year":18,"month":19,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":117},"2026\u002F08\u002Fdigital-assets\u002Fwhy-we-do-not-sell-compliance-advisory","why-we-do-not-sell-compliance-advisory","“Compliance advisory” is a phrase that hides three different jobs:\n\n1. **Legal and licensing**: counsel's job.\n2. **Policy theatre**: documents nobody runs.\n3. **Production controls and evidence**: what operators actually need on Tuesday.\n\nWe only do (3), and we deliver it as **applications**.\n\n## What we build\n\n- Control and evidence models tied to a workflow\n- Case management for KYC\u002FKYB, KYT and Travel Rule alerts\n- Dual-control and approval workflows\n- Exception registers and evidence packs generated from the work itself\n\nSee [Compliance Operations & Evidence](\u002Findustries\u002Fdigital-assets).\n\n## What we will not sell\n\n- Jurisdiction shopping\n- “We'll get you licensed”\n- Securities or virtual-asset opinions\n- Speaking to the regulator as your representative\n- Generic AML opinions\n\nIf your RFP is mostly (1), hire counsel.\nIf your pain is (3), [bring us the workflow](\u002Fcontact).\n\n## Why this is commercial, not only ethical\n\nBlurred advisory is how firms end up in two years of “strategic conversations.” A fixed application scope is how production shows up.\n\n[How we work](\u002Fcompany\u002Fhow-we-work)\n\n**Next step:** If a proposal reads like a law-firm brochure, it is not from us, even if the logo is crypto.\n\n*Fence: Application engineering and operating-model implementation only.*\n","\u003Cp>“Compliance advisory” is a phrase that hides three different jobs:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Legal and licensing\u003C\u002Fstrong>: counsel's job.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Policy theatre\u003C\u002Fstrong>: documents nobody runs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Production controls and evidence\u003C\u002Fstrong>: what operators actually need on Tuesday.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>We only do (3), and we deliver it as \u003Cstrong>applications\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch2>What we build\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Control and evidence models tied to a workflow\u003C\u002Fli>\n\u003Cli>Case management for KYC\u002FKYB, KYT and Travel Rule alerts\u003C\u002Fli>\n\u003Cli>Dual-control and approval workflows\u003C\u002Fli>\n\u003Cli>Exception registers and evidence packs generated from the work itself\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See \u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Compliance Operations & Evidence\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>What we will not sell\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Jurisdiction shopping\u003C\u002Fli>\n\u003Cli>“We'll get you licensed”\u003C\u002Fli>\n\u003Cli>Securities or virtual-asset opinions\u003C\u002Fli>\n\u003Cli>Speaking to the regulator as your representative\u003C\u002Fli>\n\u003Cli>Generic AML opinions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If your RFP is mostly (1), hire counsel.\nIf your pain is (3), \u003Ca href=\"\u002Fcontact\">bring us the workflow\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>Why this is commercial, not only ethical\u003C\u002Fh2>\n\u003Cp>Blurred advisory is how firms end up in two years of “strategic conversations.” A fixed application scope is how production shows up.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Fcompany\u002Fhow-we-work\">How we work\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If a proposal reads like a law-firm brochure, it is not from us, even if the logo is crypto.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Application engineering and operating-model implementation only.\u003C\u002Fem>\u003C\u002Fp>\n","Why we do not sell “compliance advisory”","We do not sell legal advice or policy theatre. We sell production controls and evidence, productized as fixed offers.",[45,15,14,11],"2026-08-31T00:00:00.000Z",10,{"id":119,"slug":120,"body":121,"html":122,"title":123,"description":124,"category":11,"tags":125,"author":16,"date":126,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":127},"2026\u002F09\u002Fdigital-assets\u002Fnot-a-bank-modernization-brochure","not-a-bank-modernization-brochure","We used to sound like every other deck in the building: SWIFT, CBDC curiosity, tokenization strategy, platform deploy next.\n\nThat story is wide. It is also slow, and it rarely ends in a production application.\n\n## What changed\n\nWe now work as an [enterprise AI application factory](\u002Ffactory). Every engagement starts from a named workflow and the closest deployment-ready application foundation. That holds for a bank's reconciliation queue, a ministry's case backlog, or a licensed operator's transfer workflow.\n\nBanks and insurers are firmly in scope. What we avoid is the *brochure*: multi-year modernization narratives with no named workflow, no owner and no build decision.\n\n## Who buys digital-asset applications\n\nFor the [digital assets vertical](\u002Findustries\u002Fdigital-assets), the best buyers are licensed operators with a **production gap**: VASPs, regulated exchanges, payment-token operators, custodians and tokenization platforms, where the CCO or COO can own one workflow.\n\n## What slows everything down\n\n- Innovation labs with no production owner\n- “Help us launch a token” without counsel\n- Eighteen-month RFPs as a first engagement\n\nNone of these are banned. They just need a named workflow before we can help.\n\n**Next step:** If you have a workflow stuck between pilot and production, [bring it to us](\u002Fcontact). If you need a brochure, we are the wrong vendor.\n\n*Fence: Not a VASP. Application engineering only.*\n","\u003Cp>We used to sound like every other deck in the building: SWIFT, CBDC curiosity, tokenization strategy, platform deploy next.\u003C\u002Fp>\n\u003Cp>That story is wide. It is also slow, and it rarely ends in a production application.\u003C\u002Fp>\n\u003Ch2>What changed\u003C\u002Fh2>\n\u003Cp>We now work as an \u003Ca href=\"\u002Ffactory\">enterprise AI application factory\u003C\u002Fa>. Every engagement starts from a named workflow and the closest deployment-ready application foundation. That holds for a bank's reconciliation queue, a ministry's case backlog, or a licensed operator's transfer workflow.\u003C\u002Fp>\n\u003Cp>Banks and insurers are firmly in scope. What we avoid is the \u003Cem>brochure\u003C\u002Fem>: multi-year modernization narratives with no named workflow, no owner and no build decision.\u003C\u002Fp>\n\u003Ch2>Who buys digital-asset applications\u003C\u002Fh2>\n\u003Cp>For the \u003Ca href=\"\u002Findustries\u002Fdigital-assets\">digital assets vertical\u003C\u002Fa>, the best buyers are licensed operators with a \u003Cstrong>production gap\u003C\u002Fstrong>: VASPs, regulated exchanges, payment-token operators, custodians and tokenization platforms, where the CCO or COO can own one workflow.\u003C\u002Fp>\n\u003Ch2>What slows everything down\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Innovation labs with no production owner\u003C\u002Fli>\n\u003Cli>“Help us launch a token” without counsel\u003C\u002Fli>\n\u003Cli>Eighteen-month RFPs as a first engagement\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>None of these are banned. They just need a named workflow before we can help.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If you have a workflow stuck between pilot and production, \u003Ca href=\"\u002Fcontact\">bring it to us\u003C\u002Fa>. If you need a brochure, we are the wrong vendor.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Not a VASP. Application engineering only.\u003C\u002Fem>\u003C\u002Fp>\n","Not a modernization brochure","Why fazeZERO sells named workflows on a proven architecture instead of transformation brochures, and who buys digital-asset applications.",[34,14,33,11],"2026-09-01T00:00:00.000Z",11,{"id":129,"slug":130,"body":131,"html":132,"title":133,"description":134,"category":11,"tags":135,"author":16,"date":136,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":137},"2026\u002F09\u002Fdigital-assets\u002Fwhy-fifty-percent-deposit-is-non-negotiable","why-fifty-percent-deposit-is-non-negotiable","Free diagnostics train the market to extract senior time and then go quiet.\n\nOur engagements are **fixed-scope**. **50% on signature to start.** The remainder is due on delivery, or as written in the statement of work.\n\n## What the deposit buys both sides\n\n- The calendar is real.\n- Access and owners are real.\n- Scope arguments happen once, in writing.\n- Nobody runs a charity discovery practice dressed up as enterprise sales.\n\n## What we will not do\n\n- Multi-week unpaid “assessments” that recreate a sprint\n- Start work on verbal enthusiasm\n- Expand to a second workflow without a change order\n\nLight qualification is free. Detailed solution engineering, starting with the [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint), is paid.\n\n[How we work](\u002Fcompany\u002Fhow-we-work) · [Services](\u002Fservices)\n\n**Next step:** If a deposit is impossible, the organization is not ready, or we are not the vendor. Either answer is useful.\n\n*Fence: Commercial terms do not change the regulatory fence.*\n","\u003Cp>Free diagnostics train the market to extract senior time and then go quiet.\u003C\u002Fp>\n\u003Cp>Our engagements are \u003Cstrong>fixed-scope\u003C\u002Fstrong>. \u003Cstrong>50% on signature to start.\u003C\u002Fstrong> The remainder is due on delivery, or as written in the statement of work.\u003C\u002Fp>\n\u003Ch2>What the deposit buys both sides\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>The calendar is real.\u003C\u002Fli>\n\u003Cli>Access and owners are real.\u003C\u002Fli>\n\u003Cli>Scope arguments happen once, in writing.\u003C\u002Fli>\n\u003Cli>Nobody runs a charity discovery practice dressed up as enterprise sales.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What we will not do\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Multi-week unpaid “assessments” that recreate a sprint\u003C\u002Fli>\n\u003Cli>Start work on verbal enthusiasm\u003C\u002Fli>\n\u003Cli>Expand to a second workflow without a change order\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Light qualification is free. Detailed solution engineering, starting with the \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>, is paid.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Fcompany\u002Fhow-we-work\">How we work\u003C\u002Fa> · \u003Ca href=\"\u002Fservices\">Services\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If a deposit is impossible, the organization is not ready, or we are not the vendor. Either answer is useful.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Commercial terms do not change the regulatory fence.\u003C\u002Fem>\u003C\u002Fp>\n","Why 50% deposit is non-negotiable","Fixed-fee offers start with a fifty percent deposit. It makes the calendar, owners, and scope real before work begins.",[34,14,15,11],"2026-09-02T00:00:00.000Z",12,{"id":139,"slug":140,"body":141,"html":142,"title":143,"description":144,"category":11,"tags":145,"author":16,"date":146,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":147},"2026\u002F09\u002Fdigital-assets\u002Fsheets-email-and-the-source-of-truth","sheets-email-and-the-source-of-truth","Tools can be live while the **source of truth** is still a spreadsheet.\n\nSymptoms:\n\n- Reconciliation done in Excel after the chain has moved.\n- Approvals in email with no link to a work item.\n- The “master” client list on a personal drive.\n- An exception log that is really a Slack search.\n\n## The production question\n\nFor the one workflow that matters: **where does the system of record live, and can dual control and evidence attach to it?**\n\nIf the answer is “several places,” you do not have production. You have a collage.\n\n## What changes it\n\nA [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint) forces an honest as-is map. Then the operating application becomes the system of record for that workflow, with queues, approvals, exceptions, reconciliation and evidence. It integrates with the systems you actually run instead of a future platform fantasy.\n\nWe are not religious about vendors. We are religious about **one path you can defend**.\n\n[Digital asset applications](\u002Findustries\u002Fdigital-assets)\n\n**Next step:** Screenshot the real source of truth, even if it's ugly, and [bring it to us](\u002Fcontact). A pretty architecture without a source of truth is fiction.\n\n*Fence: Implementation on your stack. No rip-and-replace.*\n","\u003Cp>Tools can be live while the \u003Cstrong>source of truth\u003C\u002Fstrong> is still a spreadsheet.\u003C\u002Fp>\n\u003Cp>Symptoms:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Reconciliation done in Excel after the chain has moved.\u003C\u002Fli>\n\u003Cli>Approvals in email with no link to a work item.\u003C\u002Fli>\n\u003Cli>The “master” client list on a personal drive.\u003C\u002Fli>\n\u003Cli>An exception log that is really a Slack search.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>The production question\u003C\u002Fh2>\n\u003Cp>For the one workflow that matters: \u003Cstrong>where does the system of record live, and can dual control and evidence attach to it?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If the answer is “several places,” you do not have production. You have a collage.\u003C\u002Fp>\n\u003Ch2>What changes it\u003C\u002Fh2>\n\u003Cp>A \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa> forces an honest as-is map. Then the operating application becomes the system of record for that workflow, with queues, approvals, exceptions, reconciliation and evidence. It integrates with the systems you actually run instead of a future platform fantasy.\u003C\u002Fp>\n\u003Cp>We are not religious about vendors. We are religious about \u003Cstrong>one path you can defend\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Digital asset applications\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Screenshot the real source of truth, even if it's ugly, and \u003Ca href=\"\u002Fcontact\">bring it to us\u003C\u002Fa>. A pretty architecture without a source of truth is fiction.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Implementation on your stack. No rip-and-replace.\u003C\u002Fem>\u003C\u002Fp>\n","Sheets, email, and the source of truth","Tools can be live while the source of truth is still a spreadsheet. Production needs one system of record you can defend.",[14,15,33,11],"2026-09-03T00:00:00.000Z",13,{"id":149,"slug":150,"body":151,"html":152,"title":153,"description":154,"category":11,"tags":155,"author":16,"date":156,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":157},"2026\u002F09\u002Fdigital-assets\u002Ffirst-ninety-days-after-licence","first-ninety-days-after-licence","The licence date is a starting gun, not a finish line.\n\nIn the first 90 days, volume either inherits a **system** or a **mess**. Hiring will not finish in time. Vendors will not wire themselves. Counsel will not run dual control.\n\n## If you are already licensed\n\nPut production in place for **one** workflow before you celebrate the second product line. Start with a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint), then configure the operating application in an [AI Production Sprint](\u002Fservices\u002Fai-production-sprint).\n\n## If you are still applying\n\nCounsel owns the licence.\nAny day-one operational design (RACI, dual-control model, evidence design) happens as a counsel-led engagement. It is not filing, not opinions, and not “we get you licensed.”\n\n## If you just became CCO\n\nYour first ninety days are the cheapest moment to make the work item the evidence and to put in dual control that survives Tuesday. After that, workarounds harden into habits.\n\n[Digital asset applications](\u002Findustries\u002Fdigital-assets)\n\n**Next step:** Congratulations posts are cheap. A named workflow is worth more. [Bring it to us](\u002Fcontact).\n\n*Fence: We do not obtain licences. Counsel does.*\n","\u003Cp>The licence date is a starting gun, not a finish line.\u003C\u002Fp>\n\u003Cp>In the first 90 days, volume either inherits a \u003Cstrong>system\u003C\u002Fstrong> or a \u003Cstrong>mess\u003C\u002Fstrong>. Hiring will not finish in time. Vendors will not wire themselves. Counsel will not run dual control.\u003C\u002Fp>\n\u003Ch2>If you are already licensed\u003C\u002Fh2>\n\u003Cp>Put production in place for \u003Cstrong>one\u003C\u002Fstrong> workflow before you celebrate the second product line. Start with a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>, then configure the operating application in an \u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>If you are still applying\u003C\u002Fh2>\n\u003Cp>Counsel owns the licence.\nAny day-one operational design (RACI, dual-control model, evidence design) happens as a counsel-led engagement. It is not filing, not opinions, and not “we get you licensed.”\u003C\u002Fp>\n\u003Ch2>If you just became CCO\u003C\u002Fh2>\n\u003Cp>Your first ninety days are the cheapest moment to make the work item the evidence and to put in dual control that survives Tuesday. After that, workarounds harden into habits.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"\u002Findustries\u002Fdigital-assets\">Digital asset applications\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> Congratulations posts are cheap. A named workflow is worth more. \u003Ca href=\"\u002Fcontact\">Bring it to us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: We do not obtain licences. Counsel does.\u003C\u002Fem>\u003C\u002Fp>\n","The first 90 days after the licence","The licence date is a starting gun. The first ninety days either inherit a system for one workflow or a mess.",[13,14,33,11],"2026-09-04T00:00:00.000Z",14,{"id":159,"slug":160,"body":161,"html":162,"title":163,"description":164,"category":11,"tags":165,"author":16,"date":167,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":168},"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.",[45,166,14,11],"aml","2026-09-05T00:00:00.000Z",15,{"id":170,"slug":171,"body":172,"html":173,"title":174,"description":175,"category":176,"tags":177,"author":16,"date":180,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":181},"2026\u002F09\u002Findustry-applications\u002Fcanada-rail-readiness","canada-rail-readiness","RTR, ISO 20022 and audit pressure create real work. They also attract brochureware.\n\nMost rail-readiness gaps are not in the messaging standard. They are in the **operating model** around it: who approves what, how exceptions are handled, how reconciliation closes, and where evidence lives when the auditor asks.\n\n## Where teams fall behind\n\n- Payment operations still run on spreadsheets while the rail narrative is ready.\n- Exception queues are shared inboxes.\n- ISO 20022 data is richer than the processes that consume it.\n- Evidence of controls is rebuilt by hand for each audit.\n\n## What helps\n\nThe same pattern we apply everywhere: one named workflow, an honest as-is, a to-be with controls and evidence, and then an **application** that runs it. Our [financial services](\u002Findustries\u002Ffinancial-services) foundations for payments operations, exception handling and reconciliation are built on the same architecture as the rest of the inventory.\n\n## What we are not\n\n- A PSP\n- A money transmitter\n- An endorsed Payments Canada program\n\nPayments and financial infrastructure is a future vertical for us, not a current public offer. If you have rail pressure (RTR, ISO 20022 or audit) and one process that keeps breaking, [tell us](\u002Fcontact). We'll say whether we fit.\n\n*Fence: Not a PSP. Not money transmission.*\n","\u003Cp>RTR, ISO 20022 and audit pressure create real work. They also attract brochureware.\u003C\u002Fp>\n\u003Cp>Most rail-readiness gaps are not in the messaging standard. They are in the \u003Cstrong>operating model\u003C\u002Fstrong> around it: who approves what, how exceptions are handled, how reconciliation closes, and where evidence lives when the auditor asks.\u003C\u002Fp>\n\u003Ch2>Where teams fall behind\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Payment operations still run on spreadsheets while the rail narrative is ready.\u003C\u002Fli>\n\u003Cli>Exception queues are shared inboxes.\u003C\u002Fli>\n\u003Cli>ISO 20022 data is richer than the processes that consume it.\u003C\u002Fli>\n\u003Cli>Evidence of controls is rebuilt by hand for each audit.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What helps\u003C\u002Fh2>\n\u003Cp>The same pattern we apply everywhere: one named workflow, an honest as-is, a to-be with controls and evidence, and then an \u003Cstrong>application\u003C\u002Fstrong> that runs it. Our \u003Ca href=\"\u002Findustries\u002Ffinancial-services\">financial services\u003C\u002Fa> foundations for payments operations, exception handling and reconciliation are built on the same architecture as the rest of the inventory.\u003C\u002Fp>\n\u003Ch2>What we are not\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A PSP\u003C\u002Fli>\n\u003Cli>A money transmitter\u003C\u002Fli>\n\u003Cli>An endorsed Payments Canada program\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Payments and financial infrastructure is a future vertical for us, not a current public offer. If you have rail pressure (RTR, ISO 20022 or audit) and one process that keeps breaking, \u003Ca href=\"\u002Fcontact\">tell us\u003C\u002Fa>. We'll say whether we fit.\u003C\u002Fp>\n\u003Cp>\u003Cem>Fence: Not a PSP. Not money transmission.\u003C\u002Fem>\u003C\u002Fp>\n","Canada rail readiness is an operating-model problem","RTR and ISO 20022 readiness is mostly process, controls and evidence. Notes on where payment operations fall behind the rail narrative.","industry-applications",[178,65,14,179],"payments","financial-services","2026-09-06T00:00:00.000Z",16,{"id":183,"slug":184,"body":185,"html":186,"title":187,"description":188,"category":11,"tags":189,"author":16,"date":190,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":191},"2026\u002F09\u002Fdigital-assets\u002Fhow-to-book-a-fit-call","how-to-book-a-fit-call","The fastest first conversation starts with the right facts. When you [contact us](\u002Fcontact), include:\n\n1. **The organization**, plus the licensed entity or regulatory context if it matters\n2. **One workflow** you want in production\n3. **Who owns it**, and whether a decision-maker will be in the room\n4. **Your AI backlog**: how many use cases you have identified or prototyped that are not yet in production\n5. **The stack already live** that the workflow touches\n6. **Any hard dates**: an exam, an audit, a launch\n\nBefore we talk, we match your problem against our application inventory.\n\n## We will answer\n\n**Yes**, with the recommended next step (usually a [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint)). **Later**, with what must change first. **No**, when we are not a fit.\n\n## Please do not book if\n\n- You want a free multi-week diagnostic\n- You need us to hold keys or file a licence\n- You cannot name an owner\n- You want a free, bespoke proof of concept\n\n[Contact](\u002Fcontact) · [Services](\u002Fservices) · [How we work](\u002Fcompany\u002Fhow-we-work)\n\n*The first conversation checks fit. It is not free delivery of the sprint.*\n","\u003Cp>The fastest first conversation starts with the right facts. When you \u003Ca href=\"\u002Fcontact\">contact us\u003C\u002Fa>, include:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>The organization\u003C\u002Fstrong>, plus the licensed entity or regulatory context if it matters\u003C\u002Fli>\n\u003Cli>\u003Cstrong>One workflow\u003C\u002Fstrong> you want in production\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Who owns it\u003C\u002Fstrong>, and whether a decision-maker will be in the room\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Your AI backlog\u003C\u002Fstrong>: how many use cases you have identified or prototyped that are not yet in production\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The stack already live\u003C\u002Fstrong> that the workflow touches\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Any hard dates\u003C\u002Fstrong>: an exam, an audit, a launch\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Before we talk, we match your problem against our application inventory.\u003C\u002Fp>\n\u003Ch2>We will answer\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Yes\u003C\u002Fstrong>, with the recommended next step (usually a \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>). \u003Cstrong>Later\u003C\u002Fstrong>, with what must change first. \u003Cstrong>No\u003C\u002Fstrong>, when we are not a fit.\u003C\u002Fp>\n\u003Ch2>Please do not book if\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>You want a free multi-week diagnostic\u003C\u002Fli>\n\u003Cli>You need us to hold keys or file a licence\u003C\u002Fli>\n\u003Cli>You cannot name an owner\u003C\u002Fli>\n\u003Cli>You want a free, bespoke proof of concept\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"\u002Fcontact\">Contact\u003C\u002Fa> · \u003Ca href=\"\u002Fservices\">Services\u003C\u002Fa> · \u003Ca href=\"\u002Fcompany\u002Fhow-we-work\">How we work\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>The first conversation checks fit. It is not free delivery of the sprint.\u003C\u002Fem>\u003C\u002Fp>\n","How to bring us a use case","What to include when you contact fazeZERO so the first conversation starts from the closest application foundation, not a blank page.",[34,14,11],"2026-09-07T00:00:00.000Z",17,{"id":193,"slug":194,"body":195,"html":196,"title":197,"description":198,"category":11,"tags":199,"author":16,"date":200,"year":18,"month":107,"quarter":20,"status":21,"featured":22,"series":23,"seriesOrder":201},"2026\u002F09\u002Fdigital-assets\u002Fwhat-we-will-not-do","what-we-will-not-do","Clarity is a sales tool.\n\n## We will not\n\n- Hold keys, custody assets, or take owner or root admin access\n- Advise on virtual-asset purchases or act as a broker\n- Issue tokens or sell issuance design as a product\n- File or obtain VARA, ADGM, CBUAE (or other) licences. Counsel does.\n- Act as a payment service provider or run a corridor\n- Guarantee an exam pass, a licence grant or a regulatory outcome\n- Run unpaid multi-week diagnostics or build free, bespoke proofs of concept\n\n## We will\n\n- Deliver three engagements: [Solution Definition Sprint](\u002Fservices\u002Fsolution-definition-sprint), [AI Production Sprint](\u002Fservices\u002Fai-production-sprint) and [Application Family Program](\u002Fservices\u002Fapplication-family-program)\n- Build operating applications with dual control and evidence on **your** stack\n- Print the fence in the statement of work\n- [Take a deposit to start](\u002Fblog\u002Fwhy-fifty-percent-deposit-is-non-negotiable)\n- Say no when we are not the right team\n\nThe full fence is in [How we work](\u002Fcompany\u002Fhow-we-work).\n\n**Next step:** If you need something on the will-not list, we are the wrong firm, and that is fine.\n\n*Implementation services under a mainland DLT \u002F cloud licence. Not a VASP. No custody, no keys, no licence filing, no VA advisory.*\n","\u003Cp>Clarity is a sales tool.\u003C\u002Fp>\n\u003Ch2>We will not\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Hold keys, custody assets, or take owner or root admin access\u003C\u002Fli>\n\u003Cli>Advise on virtual-asset purchases or act as a broker\u003C\u002Fli>\n\u003Cli>Issue tokens or sell issuance design as a product\u003C\u002Fli>\n\u003Cli>File or obtain VARA, ADGM, CBUAE (or other) licences. Counsel does.\u003C\u002Fli>\n\u003Cli>Act as a payment service provider or run a corridor\u003C\u002Fli>\n\u003Cli>Guarantee an exam pass, a licence grant or a regulatory outcome\u003C\u002Fli>\n\u003Cli>Run unpaid multi-week diagnostics or build free, bespoke proofs of concept\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>We will\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Deliver three engagements: \u003Ca href=\"\u002Fservices\u002Fsolution-definition-sprint\">Solution Definition Sprint\u003C\u002Fa>, \u003Ca href=\"\u002Fservices\u002Fai-production-sprint\">AI Production Sprint\u003C\u002Fa> and \u003Ca href=\"\u002Fservices\u002Fapplication-family-program\">Application Family Program\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Build operating applications with dual control and evidence on \u003Cstrong>your\u003C\u002Fstrong> stack\u003C\u002Fli>\n\u003Cli>Print the fence in the statement of work\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fblog\u002Fwhy-fifty-percent-deposit-is-non-negotiable\">Take a deposit to start\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Say no when we are not the right team\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The full fence is in \u003Ca href=\"\u002Fcompany\u002Fhow-we-work\">How we work\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Next step:\u003C\u002Fstrong> If you need something on the will-not list, we are the wrong firm, and that is fine.\u003C\u002Fp>\n\u003Cp>\u003Cem>Implementation services under a mainland DLT \u002F cloud licence. Not a VASP. No custody, no keys, no licence filing, no VA advisory.\u003C\u002Fem>\u003C\u002Fp>\n","What we will not do","We will not hold keys, file licences, or guarantee an exam. The public offers are fixed implementation work on your stack.",[15,45,13,11],"2026-09-08T00:00:00.000Z",18,1790080513865]