Flagship — Conduct & Financial Crime

Functional-equivalence assurance.

The CLARITY-Act fight has surfaced, in public, the control gap a Layer 5 thesis predicts. Substantial similarity is the durable regulator frame; the yield guardrail is the live case study; the parallel conduct spine is the institution-owned answer — attested equally for bank and non-bank issuers.

Cabier Intelligence · 14 June 2026 · ~14 min read

Legislative status · verified 26 July 2026

H.R.3633 (Digital Asset Market Clarity Act) passed the House 294–134 on 17 July 2025 and sits on the Senate Legislative Calendar (General Orders, Calendar No. 423) after the Banking Committee reported a substitute on 1 June 2026. Updated merged Banking/Agriculture text was released on 22 July 2026. Senate leadership expects the pre-recess floor window to be missed, and the draft still requires 60 votes. Cabier plans on the operative regimes — state trust charters and money-transmitter licensing, OCC, FRB and FDIC prudential guidance, and EU MiCA Titles III and IV for cross-border cohorts — binding through at least 2027. Legislation is the label on the control, not the control.

Source: congress.gov, H.R.3633 (119th Congress) — legislative actions and Senate Legislative Calendar, General Orders No. 423.

What governs tokenised dollars now

Executive summary

The Digital Asset Market CLARITY Act cleared the Senate Banking Committee on a fifteen-to-nine bipartisan vote on 14 May 2026 and now needs sixty votes on the Senate floor. The largest banking trades are running a functional-equivalence argument: deposit-like funds should carry bank-grade rules. The dissent argues the bill carves a hole in securities law. Senator Mark Warner is the swing, conditional on stronger investor and DeFi protections. None of those positions can be settled in statute alone. Legislation can divide jurisdiction. It cannot attest that operational controls work, and it cannot attest that they apply equally to a bank and to a digital-asset issuer. That residual is institution-owned. It is what Cabier calls Layer 5.

The shipped six institutional obligations form an integrity / settlement spine — they attest that the token issues, settles, custodies and unwinds correctly. They do not attest that the issuer behaves lawfully toward consumers and the system. The parallel conduct spine — obligations 07 through 09 — closes that gap, runs on the same evidence engine, and expresses each outcome as substantial similarity to a configurable named-regime baseline.

Demand · Coverage · Verdict

Asset segregation: Obligation 02; Covered.
Redemption / wind-down: Obligation 05; Covered.
Sanctions / screening: Obligation 06; Partial — operational screening attested; programme-effectiveness review sits in 07.
Disclosure adequacy: Obligation 04; Partial — reward-mechanics disclosure sits in 09.
Reserves / liquidity for yield: —; Gap. Closed by 09 (FR-09-02).
AML programme effectiveness: —; Gap. Closed by 07 (eight sub-controls).
Illicit-flow tracing / consumer fraud: —; Gap. Closed by 08.
Yield classification, consumer fairness: —; Gap. Closed by 09.

Substantial similarity — the durable frame

Substantial similarity is a regulator-language phrase with a long half-life. It does not turn on a specific bill section, nor on the political configuration of a given Congress. It turns on whether a programme's outcomes — for customer due diligence, suspicious-activity reporting, sanctions screening, reserve adequacy, consumer disclosure, complaint handling — are functionally equivalent to those of a bank-grade programme. That framing survives a CLARITY passage with amendments, a slip past the August recess, or a revival in a future Congress. The institutional infrastructure has to be designed to outlast the politics, and the outlasting instrument is a determination that expresses equivalence rather than one that cites a clause.

The control-axis gap

Mapping the banks' and senators' explicit demand set against the six obligations already on the platform yields a clean finding: the strength sits where the fight is not, and the silence sits exactly where it is. Custody and segregation, orderly wind-down, and cross-border conduct are already covered. The unattested surfaces are full AML programme effectiveness, on-chain illicit-flow tracing and consumer fraud, reserves and liquidity supporting any yield, and the classification of yield and reward structures themselves. Those are conduct obligations by nature — they attest issuer behaviour, not rail behaviour — and they belong at Layer 5 by definition because no rail operator can discharge them.

The yield-guardrail case study

Yield is the single provision blocking the floor vote. The trades read the bill as permitting interest-like rewards on stablecoin balances without bank-style protections. The dissent reads it as exposing consumers to unregistered investment contracts. Both read the same provision; both arrive at deposit-substitute risk. Obligation 09 converts that politically live question into an evidence-graded attestation. The classification engine (FR-09-01) returns a determination on an investment-contract analysis with a rationale category — without exposing scoring weights. The reserve, capital and liquidity surface (FR-09-02) attests at-par redemption capacity supporting any yield offered. The disclosure surface (FR-09-03) attests adequacy under Regulation DD analogues. Conformance to the published Cabier Protocol Yield-Guardrail Standard (FR-09-06) resolves against a versioned standard — the SWIFT/ISO-style move that seeds the durable instrument.

The point of the case study is not to predict the legislative outcome. It is to demonstrate that a determination engine plus a versioned standard converts a binary statutory question into an attestation that survives either outcome and applies equally to a bank-issued tokenised deposit and a non-bank stablecoin.

Three poles — banks, dissent, swing

The banks (Jamie Dimon's public position, joined by the ABA, BPI, CBA, Financial Services Forum, ICBA and NBA) run the functional-equivalence argument and have narrowed their concrete asks to two — strengthen the yield guardrails and tighten Section 404. The dissent (Senator Warren and aligned Democrats) argues the bill carves a hole in securities law and exposes consumers to fraud; forty-four amendments were filed and none passed. The swing (Senator Warner, with sponsor Senator Scott on the affirmative side) has signalled support contingent on stronger investor and DeFi protections. The institutional read is that all three poles converge on the same residual — an attestation that the issuer's conduct produces bank-grade outcomes, irrespective of charter type. The conduct spine is engineered to that residual.

Enforcement-equivalence, not "AML absent"

A precision matters here. Section 110 of CLARITY already designates digital-commodity brokers, dealers and exchanges as financial institutions under the Bank Secrecy Act. The 2025 GENIUS Act already brings payment stablecoins under the BSA. The real residual is enforcement-equivalence and deposit-substitute risk — not a literal absence of AML text. Overstating the gap is attackable, and the conduct spine is positioned accordingly: it attests that the programme produces bank-grade outcomes in practice, that the model-driven sub-controls are governed under SR 11-7, and that the determination is signed by accountable individuals under the 3LOD model. It does not assert that AML statute is missing.

The parallel conduct spine

Obligation 07 — Financial-Crime Controls — covers customer due diligence, the customer risk-rating model, transaction-monitoring coverage and tuning, SAR/STR generation, sanctions screening (cross-linked to Obligation 06), the Travel Rule, recordkeeping, and an independent programme-effectiveness review. The output is an AML Programme Effectiveness Grade and a Substantial-Similarity Attestation. Obligation 08 — Fraud & Illicit-Flow Assurance — covers consumer-fraud and scam controls, the fraud-detection model, on-chain illicit-flow tracing through a chain-analytics adapter, counterparty and VASP exposure, real-time intervention linked to L3 smart-contract primitives, and loss / reimbursement governance. The output is a Fraud-Control Effectiveness Grade and an Illicit-Flow Exposure Attestation. Obligation 09 — Yield / Product Classification & Consumer Fairness — covers the classification engine, reserves and liquidity, disclosure adequacy, the redemption guarantee (cross-linked to Obligation 05), complaint handling and Yield-Guardrail Standard conformance. The output is a Product-Classification Determination, a Yield-Guardrail Attestation, and a Consumer-Fairness Grade.

Each obligation carries a cluster attribute — INTEGRITY or CONDUCT — so the platform renders the parallel spine today and can flip to a unified 1–9 presentation without a rebuild. The Conduct Resilience Sub-Score rolls up into the ORS via the existing unexposed weighting. Calibration is neither altered nor disclosed.

AI Assurance OS as the model-attestation binding

Three sub-controls bind to the AI Assurance OS: the customer risk-rating model (FR-07-02), the transaction-monitoring models (FR-07-03), and the fraud-detection model (FR-08-02). The binding supplies the model registry, the SR 11-7 workflow and the bias-audit evidence on which each model-driven attestation depends. This is where the AI Assurance OS earns its place in the Cohort B narrative — not as a separate product line, but as the model-risk infrastructure that makes the conduct spine's model-driven sub-controls attestable in the first place.

The Cabier Protocol — standard-publication path

FR-09-06 attests conformance to a versioned Cabier Protocol standard — the Yield-Guardrail / Substantial-Similarity standard, structurally a CDS / CEF / COM / CTRE extension. The Protocol is the standard-publication vehicle through the Foundation; the obligation is the institution-owned attestation against it. The strategic move is SWIFT/ISO-style: publish the standard during the markup-to-floor window, so the institutional referent for yield-guardrail conformance exists independent of whether the bill passes, slips, or returns in the next Congress.

References and citations

Primary sources. Positions change; verify at source before relying on any figure or determination.

1Bank for International Settlements, Committee on Payments and Market Infrastructures and IOSCO, Principles for Financial Market Infrastructures — Equivalence baseline for settlement finality and operational reliability.Source
2European Union, Regulation (EU) 2023/1114 (MiCA) and the DLT Pilot Regime (Regulation (EU) 2022/858) — Comparative regimes used in the functional-equivalence mapping.Source
3Basel Committee on Banking Supervision, Prudential treatment of cryptoasset exposures (SCO60) — Capital treatment referenced in the eligibility discussion.Source
4Financial Stability Board, High-level recommendations for the regulation, supervision and oversight of crypto-asset activities and markets — Same-activity, same-risk, same-regulation framing.Source

Editorial independence. Cabier has no commercial relationship to CLARITY / GENIUS legislation and Cohort B bank-issued tokenised deposits or to the underwriters of the securities discussed in this article. Analysis is editorially independent. Cabier does not provide investment, legal or tax advice; nothing in this article is a recommendation to buy, sell or hold any security. Figures are drawn from public filings and named secondary sources current at the date of publication.

Named sources

Public legislative record and reporting — Digital Asset Market CLARITY Act committee record (15–9, 14 May 2026); GENIUS Act 2025; FDIC tokenised-deposit rulemaking; banking-trade public letters (ABA, BPI, CBA, FSF, ICBA, NBA); senator statements (Warren, Warner, Scott); BSA / FinCEN / FATF guidance. Direct citations attach on subsequent revisions.

Frequently asked questions

What is 'substantial similarity' in this context?: It is the regulator-language frame Cabier uses to assess whether an issuer's controls produce outcomes functionally equivalent to a bank-grade programme. It is durable across either CLARITY outcome because it anchors to outcome equivalence rather than to a specific bill section.
Why parallel obligations 07–09 rather than renumbering the existing six?: The shipped six form an integrity / settlement spine — they attest the token issues, settles, custodies and unwinds correctly. The new three form a conduct / financial-crime spine — they attest the issuer behaves lawfully toward consumers and the system. Each obligation carries a cluster attribute (INTEGRITY or CONDUCT) so the platform renders the parallel spine today and can flip to a unified 1–9 presentation without a rebuild. The brand of the shipped six is preserved.
Why is the yield-guardrail the lead case study?: It is the single provision blocking the Senate floor vote, the trades' most concrete and politically live ask, and the cleanest demonstration of how a determination engine plus a versioned standard can convert a binary statutory question (yield permitted yes/no) into an evidence-graded attestation that survives either legislative outcome.
Doesn't CLARITY §110 already address AML?: Yes — Section 110 designates digital-commodity brokers, dealers and exchanges as financial institutions under the Bank Secrecy Act, and the 2025 GENIUS Act already brings payment stablecoins under the BSA. The residual is enforcement-equivalence and deposit-substitute risk — not a literal absence of AML text. Cabier positions Layer 5 accordingly; overstating the gap is attackable.
What is the relationship between the conduct spine and the Cabier Protocol?: The Protocol publishes the yield-guardrail / substantial-similarity standard. Obligation 09 (FR-09-06) attests conformance to a versioned Protocol standard. The Protocol is the SWIFT/ISO-style standard-publication vehicle; the obligation is the institution-owned attestation against it.
Where does the AI Assurance OS bind?: On the model-driven sub-controls — the customer risk-rating model (FR-07-02), the transaction-monitoring models (FR-07-03), and the fraud-detection model (FR-08-02). The binding provides the model registry, SR 11-7 workflow and bias-audit evidence each obligation depends on.
What about Section 404?: The trades' second concrete ask is to tighten Section 404. The conduct spine treats Section 404 conformance as a sub-control input rather than a standalone obligation; the Yield-Guardrail Attestation (FR-09-06) is the lead institutional surface against which §404 tightening will be measured.
Does Cabier publish ORS weights, the effectiveness-grade rubric or Trust Gate internals?: No. The category map and obligation shape are public so allocators, regulators and counterparties can locate the work. The weights, rubric, dependency graph, control library and Trust Gate logic are released under signed terms only — including on the regulator surface.
How does the conduct spine treat bank versus non-bank issuers?: Identically. Each obligation runs the same evidence engine, the same effectiveness-grade rubric, and the same Substantial-Similarity engine against a configurable named-regime baseline. The outcome of the platform is that the same risk attracts the same attested rule, irrespective of charter type.
What is Cohort B?: Bank-issued tokenised deposits — the cohort the platform is currently being readied for, anchored on the TCH network with an H1 2027 target. The conduct spine applies equally to Cohort A (crypto-native issuers) and to regulated stablecoins.
What is on the regulator surface?: Read-only attestations and benchmarks only. No methodology. The supervisor view enforces the same confidentiality guardrail (XR-06) as every other surface.
What is the build phasing?: Phase C1 — Obligation 09 and the Obligation 07 core substantial-similarity engine. Phase C2 — Obligation 07 full programme, Obligation 08, AI Assurance OS bindings. Phase C3 — regulator surface, multi-jurisdiction anchor packs, and publication of the Protocol yield / substantial-similarity standard via the Foundation.
What if CLARITY does not pass?: The build is designed to a functional-equivalence standard, not a specific bill section. The conduct spine survives either outcome — passage with or without amendments, slip past August recess, or revival in the next Congress — because the underlying institutional question (does the issuer's programme produce bank-grade outcomes) does not turn on legislative timing.
How does this interact with the FDIC tokenised-deposit rule?: FR-09-02 (Reserve, capital & liquidity attestation) and FR-09-04 (Redemption guarantee & at-par convertibility) are the primary surfaces against which the FDIC rule's reserve and at-par requirements will be attested. The substantial-similarity engine expresses the outcome as functional equivalence to the FDIC baseline once finalised.
Is this a competitor to chain-analytics providers?: No. FR-08-03 integrates a chain-analytics provider as the evidence source for on-chain illicit-flow tracing. The conduct spine is the attestation layer above; chain-analytics is the data source within it.
Does Cabier publish a price for this work?: No. Every engagement is custom-quoted under signed terms; access is private-review only.
Who owns the 3LOD attestation?: Human-led. The platform supports the workflow, captures evidence, and runs the determination engines; the attestation itself is signed by accountable individuals under the 3LOD model. There is no autonomous attestation language anywhere in the spine.
How does Cabier engage on the conduct spine?: Through private review with a named institutional sponsor. The first engagement scope is typically a current-state assessment against the conduct cluster, a gap map against the existing integrity spine, and a phased remediation plan with explicit owners and timelines.

Glossary

Substantial similarity: The regulator-language standard expressing one programme's outcomes as functionally equivalent to a configurable named-regime baseline.
Functional equivalence: Outcome equivalence between two control programmes — the institutional frame the trades have advanced in the CLARITY debate.
Layer 5: The institution-owned governance layer above the tokenised settlement substrate. The residual that no rail operator can discharge.
Conduct cluster: The CONDUCT obligation cluster (07–09) — financial crime, fraud and illicit flow, yield and consumer fairness.
Integrity cluster: The INTEGRITY obligation cluster (01–06) — issuance, custody, settlement, disclosure, recovery, cross-border conduct.
Cluster attribute: A platform field on each obligation enabling the parallel-spine display today and the unified 1–9 presentation later, without rebuild.
CRSS: Conduct Resilience Sub-Score — the rollup of conduct obligation grades that feeds the ORS via the existing unexposed weighting.
ORS: Operational Resilience Score — the institutional rollup metric the platform produces. Weights are not exposed.
3LOD: Three Lines of Defence — issuer control owners (1LOD), compliance and risk (2LOD), and internal audit / external assurance (3LOD).
Trust Gate: The decision logic that authorises a graded outcome to proceed. Internals are confidential.
Substantial-Similarity engine: The shared determination layer that expresses each obligation's outcome as functional equivalence to a configurable baseline.
Yield-Guardrail Standard: The published Cabier Protocol standard against which FR-09-06 attests issuer conformance. Versioned.
CLARITY Act §110: The provision designating digital-commodity brokers, dealers and exchanges as financial institutions under the Bank Secrecy Act.
CLARITY Act §404: The provision the trades have targeted alongside yield guardrails — the source of the second concrete ask.
GENIUS Act: 2025 US legislation bringing payment stablecoins under the BSA and establishing reserve and disclosure obligations.
FDIC tokenised-deposit rule: FDIC rulemaking on reserves and at-par redemption for bank-issued tokenised deposits — currently in comment cycle.
Cabier Protocol: The standard-publication vehicle — CDS, CEF, COM, CTRE — under the Foundation. The SWIFT/ISO-style move.
AI Assurance OS: The model-risk infrastructure binding the customer-risk, transaction-monitoring and fraud-detection models — registry, SR 11-7 workflow, bias audit.
TCOS: Tokenization Control OS — the platform layer the conduct spine extends.
Cohort A: Crypto-native and non-bank issuers.
Cohort B: Bank-issued tokenised deposits. TCH network, H1 2027.
TCH: The Clearing House — the bank-owned payment network anchoring the Cohort B timeline.
Howey analysis: The US securities-law investment-contract test used as the rationale workflow inside FR-09-01.
FATF R.16: FATF Recommendation 16 — the Travel Rule on originator and beneficiary data transmission.
SR 11-7: US Federal Reserve supervisory guidance on model risk management — the binding standard for the AI Assurance OS workflow.

CLARITY / GENIUS Watch

The companion editorial hub.

Open

Conduct & Financial-Crime Spine

The vertical landing — two clusters, bindings, phasing.