The person who has to answer for this is whoever wrote "pending federal market structure" in a roadmap note and then attached a quarter to it.
The arithmetic is short. The House comes back on September 14 for four days [1]. The Senate's procedural motion to advance its version of CLARITY is set for September 15 [2]. Punchbowl News reporter Brendan Pedersen put the House's departure as early as September 17 [9], which leaves three calendar days when both chambers are in the building [15]. Cloture would only open the Senate's work: the chamber would still have to finish consideration and pass the bill, and its text is not the text the House already approved, so the versions would then need reconciling [2][3].
What is operative for a product team today is narrower than what has been pitched to it. Stablecoins have a federal statute in the GENIUS Act [4]. The broader market structure rules crypto companies actually wanted are unfinished [5]. Executive action has filled part of the gap, with orders establishing a Strategic Bitcoin Reserve and a working group told to develop a federal framework [16], but that reserve is an executive order, not a rulebook a listing committee can read.
The most expensive open question is yield. GENIUS bars stablecoin issuers from paying interest directly to holders but left room to argue about whether an affiliated company can [6]. Banking groups wanted that door closed in CLARITY; Coinbase and other crypto firms argued the banks were trying to suppress a competing product, with Brian Armstrong accusing bank lobbyists of trying to "ban their competition" [7]. If affiliate yield sits in your spec, the bill was the scheduled answer to a question that stays open without it, which is a harder line to write on a risk register than a plain no.
Teams tend to treat legislative risk as schedule risk, sliding Q1 into Q3 and letting the burn-down chart absorb it. What actually happens is different: the definitions the schema was drawn around never arrive, and everything keyed to them gets rebuilt against the regime that does exist. A classification field with a fixed set of allowed values and a disclosure template keyed to that field are speculative work, not slipped work.
Sort the roadmap on two axes. First, does the item need a new federal definition to be legal or sellable, or does it only need current rules read carefully? Second, does the item survive the text changing hands? Pedersen's warning is that CLARITY could sit until the lame duck, by which point a chamber or two could change control [9], so today's draft language is not a stable input to a spec. Anything in the needs-a-new-definition-and-depends-on-this-draft corner belongs behind a flag with no date attached. Anything that only needs current rules ships now and collects the upside if the bill ever lands.
Slippage is not uniformly bad news for the industry either. Coinbase withdrew support in January after reviewing an early Senate draft, with Armstrong saying "We'd rather have no bill than a bad bill" [11]. And the Senate's ethics negotiations, complicated by the Trump family's reported $1.4 billion crypto windfall [10], are not a variable a product manager can forecast. Any roadmap item whose legality depends on a floor vote with no date on the calendar is a bet, and staffing it as a plan is how a Q1 launch becomes a Q3 rewrite.
