On September 16th, the House Ways and Means Committee will convene to mark up legislation governing digital asset taxation. If you\u2019ve been watching the crypto media cycle, you\u2019ve likely seen this framed as a pivotal regulatory moment\u2014a potential inflection point for federal revenue, institutional adoption, and America\u2019s standing in the global digital asset hierarchy. The narrative machinery is already spinning: \u201cHistoric crypto tax legislation,\u201d \u201cwatershed moment for regulatory clarity,\u201d \u201cmake-or-break for DeFi.\u201d
Let me pull the emergency brake on that framing.
The audit trail never lies, and in this case, the trail is suspiciously thin. The information基底 for this \u201cwatershed moment\u201d consists of precisely two data points: a markup date and a vague assertion that the rules could affect federal revenue, regulatory clarity, and America\u2019s global position. No bill text. No sponsor\u2019s name. No legislative year (though September 16th is specified). No Joint Committee on Taxation scoring. No original source citation. We\u2019re being asked to evaluate a structural load-bearing event based on nothing more than a calendar invitation.
I\u2019ve spent two decades watching Washington manufacture regulatory urgency around crypto. I was in the room\u2014metaphorically, through proxies and sources\u2014when the Infrastructure Bill\u2019s broker language nearly destroyed DeFi\u2019s compliance architecture in 2021. I tracked the saga of the \u201c31\xd7 Markup\u201d and watched it consume weeks of industry bandwidth before dissolving into procedural noise. This markup follows a pattern I recognize intimately: the gap between legislative theater and actual law is measured not in months but in congressional sessions, and the gap between \u201cmarkup scheduled\u201d and \u201csomething that changes your tax bill\u201d is essentially infinite.
Let me walk you through what we actually know, what we can reasonably infer from legislative procedure, and why the narrative around this event is suffering from severe information asymmetry.
The Markup in Context: Reading the Silence Between the Blocks
Before we can assess impact, we need to understand what a markup actually is\u2014because the terminology is being weaponized to inflate significance.
A markup session is the committee\u2019s opportunity to debate, amend, and vote on legislation before it advances to the full House. It is, in procedural terms, the starting line, not the finish line. After markup, the bill must still pass the House floor, navigate the Senate\u2019s own chamber (typically requiring 60 votes to end debate on major legislation), survive conference committee if the chambers pass different versions, and receive presidential signature. Every single one of these steps is a kill point.
Tracing the logic gates behind this yield: markup is to legislation what whitepaper publication is to mainnet launch. You\u2019ve articulated intent. The hard part hasn\u2019t started.
The Ways and Means Committee holds jurisdiction over tax matters\u2014this is accurate. But tax legislation involving digital assets doesn\u2019t move through a vacuum. It intersects with the Senate Finance Committee\u2019s parallel jurisdiction, must contend with the Office of Management and Budget\u2019s scoring requirements, and exists within a broader political environment where the Federal Reserve\u2019s rate posture, the deficit trajectory, and the election calendar all function as variables that can terminate legislation mid-flight.
What do we actually know about the substance? The Committee will mark up \u201ccrypto tax rules.\u201d Beyond that: silence. The industry\u2019s known pain points\u2014the de minimis threshold question (whether buying coffee with Bitcoin should trigger a capital gains event), the wash sale rule applicability, the timing of staking income recognition, the broker definition\u2019s reach into DeFi front-ends and validators\u2014are all theoretically on the table. But the table has no visible contents.
The architecture of belief here is worth dissecting. A markup date announcement is procedurally equivalent to a company announcing \u201cwe plan to discuss product strategy in Q4.\u201d It signals intention, not outcome. Yet the crypto market\u2019s news cycle has a documented tendency to treat procedural milestones as if they were delivery confirmations.
My 2017 audit experience taught me a crucial lesson about information quality: the most dangerous analysis is the kind performed on incomplete foundations. When I was stress-testing Parity multisig contracts during the ICO boom, I watched entire market caps evaporate because people were pricing code they hadn\u2019t read. The same principle applies here. Pricing legislative impact without the text is like pricing a DeFi protocol without examining the bytecode.
Decoding the Narrative: What the Markup Actually Signals
Let me be precise about what information we have and what it implies.
The confirmed signal: The House Ways and Means Committee has scheduled a markup on digital asset tax legislation for September 16th. This is a factual statement. It tells us the Chairman has prioritized crypto tax as a committee agenda item, which implies sufficient member interest and staff capacity to draft text.
The implied signal (high confidence): This markup will likely involve a package of multiple provisions rather than a single narrow fix. The Ways and Means Committee\u2019s historical pattern for tax legislation involves comprehensive packages\u2014the Tax Cuts and Jobs Act, the SECURE Acts, the various COVID relief tax provisions. Single-topic tax bills can move, but comprehensive digital asset tax reform would almost certainly be structured as a package addressing multiple pain points simultaneously.
The probable signal (medium confidence): The markup\u2019s timing suggests it\u2019s positioned for potential inclusion in a larger legislative vehicle\u2014possibly a continuing resolution, an omnibus spending package, or a budget reconciliation bill. The Congressional calendar is governed by these larger must-pass vehicles, and tax legislation frequently hitches itself to fiscal trains that are guaranteed to run. If this markup\u2019s timing aligns with a potential reconciliation vehicle, the procedural pathway becomes more favorable than if it were moving as standalone legislation.
Now, let me trace the thread from consensus to chaos on the industry implications.
The mainstream narrative frames this as a clarity catalyst. Regulatory certainty is supposed to unlock institutional capital, reduce compliance overhead, and restore America\u2019s competitive position against jurisdictions like the EU (where MiCA has already been implemented), Singapore (which imposes no general capital gains tax), and the UAE (which has no income tax and a permissive regulatory stance toward digital assets).
This narrative isn\u2019t wrong, exactly. It\u2019s just vastly premature. Clarity requires text. Text requires markup. Markup requires passage. Passage requires surviving the Senate. And the Senate, on tax matters especially, is where legislative ambitions go to be autopsied.
Reading the silence between the blocks: the markup announcement is not a signal about outcomes. It\u2019s a signal about process entry. We\u2019ve entered the queue. The queue is long, the queue is political, and the queue has killed better-positioned legislation than this.
The Real Battleground: Broker Definitions and the Structural Threat to DeFi
If I had to identify the single most consequential dimension of crypto tax legislation\u2014the dimension that will actually determine whether this markup matters\u2014it isn\u2019t rates. It isn\u2019t the de minimis threshold. It isn\u2019t wash sale rules.
It\u2019s the broker definition.
This is the issue that will determine whether we\u2019re analyzing a compliance nuisance or a structural extinction event for non-custodial protocols.
The 2021 Infrastructure Investment and Jobs Act initially defined \u201cbroker\u201d so broadly that it would have captured validators, node operators, miners, and DeFi front-end developers under the same reporting requirements as Coinbase and Fidelity. The industry\u2019s subsequent lobbying effort\u2014which I covered extensively\u2014narrowed the definition in subsequent guidance, but the underlying legislative language remained intact. The IRS and Treasury have been operating under this cloud ever since, with the DeFi broker question unresolved at the regulatory level.
Where code meets cultural memory: the broker definition isn\u2019t just a reporting obligation. It\u2019s a design constraint imposed on the entire ecosystem. If a DeFi protocol\u2019s front-end is classified as a broker, the protocol faces an existential choice: embed KYC infrastructure (compromising its non-custodial architecture and potentially its legal status) or exit the US market (sacrificing the world\u2019s largest crypto capital base).
I\u2019ve mapped the sociological patterns of DeFi communities during stress events\u2014the Terra collapse, the FTX implosion, multiple governance attacks. The common thread isn\u2019t technical failure. It\u2019s narrative failure. Communities collapse when they lose faith in the promise the protocol made to them. For many DeFi protocols, that promise is \u201cwe are non-custodial, we don\u2019t hold your funds, we can\u2019t be compelled to report your activity.\u201d If the broker definition collapses that promise, the sociological rupture will be as significant as any smart contract bug.
The markup\u2019s potential impact on the broker definition is therefore the canary in the coal mine. If the committee text excludes DeFi front-ends and non-custodial actors from the broker definition, this is genuinely positive legislation. If it doesn\u2019t\u2014if it codifies or expands the broad definition\u2014then we\u2019re looking at something closer to a regulatory extinction event dressed up as tax reform.
We don\u2019t know. And until the text is published, any analysis of this dimension is inference based on legislative pattern recognition, not substance evaluation.
The hidden information here is significant: The primary lobbying pressure on this legislation will come not from crypto-native companies, but from the tax preparation industry, the CPA profession, and institutional broker-dealers. These are the entities that benefit directly from expanded reporting requirements\u2014more complexity means more demand for their services. Their lobbying infrastructure in Washington dwarfs what the crypto industry has built. This means the legislation\u2019s likely trajectory is toward MORE reporting obligations, not fewer, unless the crypto industry organizes a counter-lobbying effort that matches the intensity of the 2021 Infrastructure Bill campaign.
Market Pricing: Why This Event Won\u2019t Move Your Portfolio (And Why That\u2019s Fine)
Let\u2019s talk about market impact, because the commentary cycle is already building expectations.
My assessment: this markup announcement is priced at approximately zero.
Not zero in the sense that markets ignore it. Zero in the sense that the information content is so low that any price movement would be pure noise, not signal.
Here\u2019s the reasoning: institutional participants and systematic traders don\u2019t position based on markup scheduling. A committee putting something on its calendar is not a cash flow event. It\u2019s not an earnings surprise. It\u2019s not even a regulatory enforcement action. It\u2019s a procedural acknowledgment that something might happen at some point in an undetermined future.
Logic fails when greed takes the wheel if you treat process news as delivery news. The crypto market\u2019s documented tendency toward narrative overshoot\u2014the 2021 Infrastructure Bill reaction, the multiple \u201cSEC victory\u201d celebrations that preceded actual court rulings, the \u201cETF approval\u201d price explosions in anticipation of actual approval\u2014suggests that market participants will attempt to trade this event regardless of its information content. They will probably fail to generate alpha, but they will generate volume, which generates fees, which generates the illusion of significance.
The actual tradeable moment will come after the markup, when committee text becomes available for analysis. THAT is when the market can actually price substantive provisions. A markup announcement is a calendar entry. Committee text is a document that can be read, analyzed, and compared against existing law. The gap between those two events is measured in weeks or months, and it represents the only window where informed analysis can actually generate insight.
For the next several weeks, the appropriate response is not \u201cposition for the markup.\u201d It\u2019s \u201cprepare the analytical infrastructure to evaluate the text when it drops.\u201d That means: identifying which provisions affect which protocols, which token types, which user behaviors. It means building the framework before the data arrives, not scrambling to understand the implications after the market has already moved.
Following the thread from consensus to chaos: the institutional traders who will generate returns on this event are already positioned. They\u2019re reading the same thin information we all have, but they\u2019re not trading it. They\u2019re waiting for the text.
The Contrarian Angle: Why This Markup Might Be More Significant Than It Appears
Now let me stress-test my own position, because an ENTP who never challenges their own thesis is just a commentator with a Substack subscription.
The contrarian case: procedural milestones matter more than we admit, precisely because they create the preconditions for substantive action.
Every law starts as a markup. Every markup starts with an agenda decision. Agenda decisions in Congressional committees are not random. They reflect the intersection of policy priority, member interest, and political feasibility. When the Ways and Means Committee schedules a markup on digital asset taxation, it signals that the Chairman believes there is sufficient bipartisan support to advance the issue\u2014not to passage, but to advancement.
This matters for several reasons that the \u201cprocedure is too long\u201d argument discounts:
First, the legislation\u2019s existence changes the negotiating landscape. Even if this markup never becomes law, the text will exist. It will be the baseline that subsequent negotiations amend. Industry advocates will be able to engage with specific provisions rather than fighting ghosts. The difference between lobbying against an undefined \u201ctax threat\u201d and lobbying against Section 4.5(b) of H.R. XXXX is the difference between trying to push a boulder and pushing a boulder with documented friction points.
Second, the markup creates a political record. Voting records on crypto-related legislation have become increasingly salient as the industry builds its political operation. A markup vote gives industry-aligned PACs and advocacy groups concrete data on which members understand digital assets and which don\u2019t. This information is campaign infrastructure. It shapes primary challenges, endorsement decisions, and donor allocation. The legislative outcome might be zero, but the political intelligence gathered could be significant.
Third, markup timing is political signal to other actors. If the Senate is watching the House\u2019s markup, if the Administration has communicated private preferences, if the SEC and CFTC are calibrating their enforcement posture based on Congressional trajectory\u2014then even an unsuccessful markup shifts the behavior of other regulatory actors. Legislation that fails can still alter the regulatory environment by changing what other institutions believe is coming.
I\u2019m not arguing the markup will succeed. I\u2019m arguing that its significance isn\u2019t captured by \u201cprocedural milestone, probably won\u2019t become law.\u201d The significance is in the preconditions it creates and the signals it sends to a broader ecosystem of regulatory actors who are making decisions right now based on what they expect Congress to do.
The hidden variable here is budget reconciliation. If the markup text becomes available during a period when Congress is considering a reconciliation package\u2014legislation that can pass the Senate with a simple majority under the Byrd Rule\u2014then the markup\u2019s trajectory changes dramatically. Reconciliation vehicles are the nuclear option for tax legislation, and if crypto tax provisions get attached to one, the 60-vote Senate threshold evaporates. This is speculative, but it\u2019s not idle speculation. The Infrastructure Bill\u2019s broker language attached to a must-pass vehicle because the drafters understood the leverage dynamics. Same logic applies here.
Tokenomics of Tax Policy: How Compliance Costs Restructure Incentives
Let me zoom in on something that gets underappreciated in the legislative coverage: tax rules are a hidden tokenomics parameter.
A protocol\u2019s token economics typically focus on supply schedules, emission rates, staking rewards, and fee distributions. What gets ignored in this framework is that the regulatory environment determines the effective yield that token holders realize after tax obligations. A 12% staking APR sounds attractive until the regulatory framework treats staking rewards as ordinary income at receipt, subjects them to capital gains treatment upon disposition, and imposes reporting requirements that add compliance overhead equivalent to 1-2% of yield.
Unspooling the knot of innovation: the most powerful tax provisions affecting crypto aren\u2019t the ones that change rates. They\u2019re the ones that change the frequency of taxable events.
Consider the de minimis question. If Congress establishes no de minimis threshold\u2014meaning every Bitcoin payment, no matter how small, triggers a capital gains calculation\u2014then the practical usability of payment-layer tokens collapses. The compliance cost per transaction exceeds the transaction value for any payment under $100. This doesn\u2019t kill Bitcoin as an asset class. It kills Bitcoin as a payment mechanism. The distinction matters enormously for which protocols attract developer talent, user adoption, and infrastructure investment.
Similarly, if Congress extends wash sale rules to digital assets, the calculus for tax-loss harvesting changes completely. Market makers and sophisticated traders currently exploit the absence of wash sale rules to harvest losses in ways unavailable in equities markets. Extending wash sale treatment would compress these strategies, potentially reducing liquidity depth in digital asset markets. This isn\u2019t obvious from the headline \u201ctax reform\u201d\u2014it\u2019s a microstructure effect that only becomes visible when you trace the incentive chain from rule to behavior to market outcome.
The audit trail here is clear: regulatory compliance costs are passed through the ecosystem in ways that aren\u2019t always visible. A protocol that faces $500,000 in annual compliance costs must either reduce security spending, reduce token holder distributions, or increase protocol fees. None of these outcomes are neutral. The tax legislation that seems abstract and distant when it\u2019s being debated in committee becomes very concrete and immediate when it\u2019s reflected in reduced staking APRs or increased swap fees.
Ecosystem Dependencies: Mapping Who Wins and Who Loses
The legislative food chain for crypto tax policy runs from Congress down through the IRS to compliance infrastructure providers to the protocols and users at the bottom. Let\u2019s trace the dependency chain:
At the top: the Committee staff who draft the text, the Joint Committee on Taxation that scores the revenue impact, and the Congressional Budget Office that evaluates the macroeconomic assumptions. These actors control what gets proposed and how it gets classified.
Below them: the IRS, which must interpret and enforce whatever Congress passes, and the Treasury\u2019s Office of Tax Policy, which provides regulatory guidance on implementation. The IRS\u2019s existing framework\u2014Notice 2014-21 (treating crypto as property), Revenue Ruling 2019-24 (hard forks), Revenue Ruling 2023-14 (staking income at receipt)\u2014has been built through administrative guidance rather than legislation. Legislative action will either codify this framework (reducing uncertainty) or supersede it (introducing new uncertainty).
Below the IRS: the compliance infrastructure layer. Tax preparation software companies (CoinTracker, Koinly, TaxBit), institutional custodians (Coinbase Custody, Fidelity Digital Assets), and broker-dealers preparing for the 1099-DA reporting regime. These entities benefit directly from legislative complexity. More reporting requirements means more demand for their services. Their economic interest is structurally aligned with expanded compliance obligations, which means they will lobby for legislation that increases rather than decreases reporting complexity.
Below the compliance layer: the actual protocols, validators, miners, and end users who bear the compliance costs. For retail users making occasional transactions, the marginal impact of new reporting requirements is manageable. For institutional participants managing complex portfolios across multiple chains, the compliance overhead could be substantial.
The ecosystem mapping reveals a structural asymmetry: the entities with the most at stake in legislative outcomes (protocols and end users) have the least capacity to influence legislative text. The entities with the most lobbying infrastructure (compliance service providers, institutional custodians, traditional financial intermediaries) have the most to gain from legislative complexity. This isn\u2019t a conspiracy\u2014it\u2019s just the normal functioning of interest group politics. But it means the legislation that emerges from markup is likely to look more like the compliance industry\u2019s preferred outcome than the crypto ecosystem\u2019s preferred outcome.
Compliance Architecture: From IRS Guidance to Statutory Law
One of the underappreciated dimensions of this markup is the transition it represents: from administrative guidance to statutory law.
The IRS has been operating in a statutory vacuum for over a decade. Notice 2014-21 was a guidance document, not legislation. Revenue rulings are interpretive, not legislative. The IRS can change its guidance through the administrative process, which means the current framework is more flexible than legislation but also more vulnerable to reversal under different administrations.
The transition to statutory law is a double-edged sword. On one edge: statutory law provides certainty. Protocols can build around fixed requirements rather than guidance that might change. Institutional investors can price compliance costs with confidence. The ambiguity that currently characterizes digital asset taxation gets reduced.
On the other edge: statutory law locks in whatever provisions Congress enacts. If Congress gets something wrong\u2014if the broker definition is drafted too broadly, if the de minimis threshold is set at zero, if the cost basis allocation rules create perverse incentives for certain transaction types\u2014the fix requires another legislative action, which means another markup, another Senate process, another presidential signature. The flexibility of guidance is replaced by the rigidity of law.
My crisis narrative forensics background\u2014from the Terra collapse investigation to multiple protocol failure post-mortems\u2014teaches me that rigidity in the face of complexity is often more dangerous than flexibility. Protocols evolve. Token economics change. New transaction types emerge. A tax framework that works for 2024\u2019s DeFi landscape might be entirely inadequate for 2027\u2019s, but if it\u2019s locked into statute, the only escape is another legislative battle.
The hidden information here: the IRS\u2019s existing guidance has been incrementally improved through successive rulings. The 2019-24 ruling on hard forks, the 2023-14 ruling on staking, the ongoing 1099-DA implementation\u2014these represent a regulatory learning curve that statutes would interrupt. Congress legislating today would be legislating based on 2024\u2019s understanding of a technology that will look substantially different in 2027. The question of whether statutory certainty is worth the cost of locking in current understanding is a genuine policy disagreement, not a rhetorical one.
Political Feasibility: Reading the Congressional Tea Leaves
Let me apply my contrarian stress-testing to the political dynamics, because this is where most analysis either oversells certainty or uses uncertainty as an excuse to avoid making judgments.
The baseline: tax legislation in a divided government is extremely difficult to pass. The Senate requires 60 votes to end debate on most legislation, and on tax matters especially, partisan positions tend to be calcified. The political dynamics around digital assets don\u2019t map cleanly onto the traditional Democrat/Republican axis, which creates cross-aisle potential\u2014but it also creates unpredictability, because the coalitions that might form around specific provisions aren\u2019t stable.
The structural tailwind: digital assets have become a rare bipartisan issue. Republicans see them as an expression of financial freedom and an industry that generates economic growth. Democrats see them as a potential tool for financial inclusion and a sector that generates tax revenue from high earners. Both sides have reason to want the IRS to have better tools for enforcement. This convergence creates a genuine opportunity for legislation that would be impossible on most other financial regulation topics.
The structural headwind: the deficit. Any legislation that reduces tax revenue\u2014even if the reduction is offset elsewhere\u2014faces a higher hurdle in a fiscal environment where the Congressional Budget Office is projecting sustained deficits. The markup\u2019s revenue impact will be scored by the JCT, and if the score is negative, it becomes a target for opponents. Conversely, if the score is positive\u2014if the legislation is framed as enforcement rather than policy change\u2014it has a better path.
The hidden political variable: reconciliation. If the markup text is ready and waiting when Congress moves a reconciliation package\u2014and reconciliation is theoretically possible whenever the majority has the votes and the parliamentary calendar\u2014then the markup\u2019s pathway transforms from the standard legislative gauntlet to a much faster process. This is speculative, but it\u2019s the scenario that would make September 16th genuinely significant rather than procedurally interesting.
Risk Matrix: What Could Actually Go Wrong (Or Right)
Let me organize the risk landscape into a framework that goes beyond the usual \u201chigh uncertainty\u201d hand-waving.
High-probability, high-impact risks: These are the risks where we have sufficient information to assign both probability and magnitude.
The primary risk is the gap between markup announcement and actual legislative text. This gap will be filled by speculation, narrative inflation, and market participants positioning on incomplete information. The risk isn\u2019t that legislation passes\u2014it\u2019s that the market treats the markup as if it\u2019s certain to pass and prices accordingly. If the markup fails to advance, or advances with provisions weaker than the narrative had assumed, the correction could be significant.
Medium-probability, high-impact risks: These are the risks where the probability is uncertain but the impact would be substantial.
The broker definition expansion represents the highest-impact risk for DeFi specifically. If the markup text codifies or extends the broad broker definition, the structural impact on non-custodial protocols is potentially existential. This isn\u2019t a market volatility risk. It\u2019s a protocol viability risk. The probability depends on the committee\u2019s composition and the lobbying intensity of competing interests\u2014both unknown at this point.
The retroactive application risk is similarly high-impact. If the legislation applies to periods before enactment, protocols and users face the possibility of retroactive compliance obligations for transactions they executed without knowledge of future legal requirements. This would be legally contentious but not unprecedented in tax legislation.
Low-probability, high-impact upside: These are the scenarios where things go better than expected.
If the markup text excludes DeFi front-ends and non-custodial actors from the broker definition, this represents a genuine legislative win for the crypto ecosystem. It would provide certainty without imposing structural compliance costs. The probability of this outcome depends on the committee\u2019s specific composition and whether the crypto industry\u2019s lobbying operation has been effective\u2014both currently unknowable.
If the markup text includes meaningful de minimis relief\u2014a sensible threshold that exempts small transactions from capital gains calculations\u2014it would preserve the practical usability of payment-layer tokens. This is both good policy and good politics: it protects retail users while targeting enforcement resources at larger transactions.
What Actually Deserves Your Attention
Let me close with a direct assessment that cuts through the noise.
The September 16th markup is not a market event. It is a process event. The information available is insufficient to change any investment thesis, any protocol design, or any compliance strategy. The text that emerges from markup\u2014assuming markup proceeds and text is released\u2014will be the first substantive data point worth analyzing.
The analytical infrastructure you should be building now is the capability to rapidly evaluate broker definition language. This is the dimension that determines whether we\u2019re analyzing a compliance improvement or an existential threat to non-custodial protocols. Everything else\u2014rates, thresholds, timing\u2014is secondary to this structural question.
The political intelligence worth gathering now is committee member positioning. Who voted for and against crypto-related amendments in the current Congress? Whose campaigns have received donations from crypto PACs? Whose districts have significant digital asset employment? This intelligence will determine the markup\u2019s trajectory and will be essential for any lobbying effort aimed at shaping the final text.
The market positioning that makes sense is patience. There is no alpha in pre-positioning for a markup announcement. The alpha is in having the analytical framework ready when the text drops, because the text will move faster than most market participants can process, and the first 48 hours of legislative text analysis will define the narrative for the subsequent weeks.
The narrative trap to avoid is story inflation. A markup announcement is not a law. A law is not implementation. Implementation is not enforcement. And enforcement is not market impact. Each step in this chain is a distinct event with distinct probabilities, and conflating them is how you end up with positions sized for a regulatory revolution that turns out to be a committee hearing.
History rhymes, but the hash changes. The crypto regulatory landscape of 2026 will look different from 2024\u2019s in ways we can\u2019t fully anticipate. What we can do is build the analytical infrastructure to respond to whatever arrives, rather than pre-committing to narratives that the data may eventually contradict.
The markup is scheduled. The text will come. And then, for the first time, we\u2019ll have something real to analyze. Until then, the most sophisticated position is not to position at all. It\u2019s to prepare.",