The rulebook slipped. The rails did not.

The statutory deadline for the American stablecoin rulebook came and went this month without producing a rulebook. Nothing stopped. Money kept raising, protocols kept shipping, and the private standards that were supposed to sit underneath the regulation carried on setting the terms. That gap is the story this week, and it is a familiar one to anyone who has run a payments operation through a regulatory transition.

The deadline passed without the rules

Treasury and the four primary federal stablecoin regulators reached the GENIUS Act's 18 July rulemaking deadline with no final set of implementing regulations in place [1]. Several of the major proposals are still open. Comments on the joint customer identification rule run until 21 August, and an FDIC anti money laundering proposal stays open until 4 August [1]. The practical effect is that issuers now operate against a statute that is in force and a rulebook that is not finished, which extends the uncertainty rather than resolving it [2].

The banks name the fight they actually want

While the drafting continues, the incumbents have picked their ground. Banks are pressing regulators to close what they call a loophole allowing stablecoin issuers to pass yield to holders, on the argument that a yield-bearing dollar substitute pulls directly at their deposit base [3]. That is not a technical quibble about disclosure. It is a fight about where deposits sit, and it explains a good deal of why the final rules are late.

London runs its own clock

The UK is moving on a separate timetable and is further along in one respect. The Bank of England's June policy statement and draft Code of Practice for sterling-denominated systemic stablecoins are out, alongside the FCA's stablecoin issuance policy statement, PS26/10 [3]. That consultation closes on 22 September, with the Bank intending to finalise the Code by the end of the year [3]. Anyone building a settlement path that touches both jurisdictions is now designing for two rulebooks landing at different times and in different shapes.

The capital did not wait

The money moved anyway, and it moved towards controlling agents rather than paying them. Neo came out of stealth on 24 July with $100m to help enterprises govern and secure the spread of AI agents across their software, with inventory, real-time control, and policy enforcement as the pitch [4]. In the same window, Alpaca raised $135m for its self-clearing broker-dealer infrastructure, with the new capital going into an agent-first and prime-brokerage build-out [5]. Both bets read the same way. The interesting margin is no longer in letting an agent transact, it is in constraining what it is allowed to do and proving afterwards that the constraint held.

Read from the rails

A missed rulemaking deadline is not a pause. It is a handover. When the public rulebook is late, the private standard becomes the operating rule by default, and the firms that shipped a protocol in June end up defining what compliant looks like in the autumn. I have watched this happen on smaller scales during scheme migrations. The guidance slips, everyone builds to the working draft plus whatever the biggest counterparty does, and the eventual rule has to accommodate what already exists.

The part that worries me is the reconciliation obligation, because that one never slips. Whatever the final rule says about customer identification and anti money laundering treatment, the transactions being written today will be in scope when it lands. Ten years in operations taught me that you cannot retrofit an audit trail, you can only regret not having captured it. If you are running agent-initiated payments through a stablecoin leg right now, the useful work this month is not lobbying the comment window. It is making sure every payment carries the mandate it fired under, the identity it fired as, and enough of both to answer a question nobody has asked yet.

When the rulebook is late, the working draft becomes the rule. The exposure is not in what you built, it is in what you failed to record while you were building it.