That one is the anti-corruption finding. It rests on Brazilian criminal and judicial conduct rather than on a measured effect on United States trade. The point is not that anti-corruption is missing from Section 301. It is that the anti-corruption finding depends on a commerce nexus the determination states at the level of competitive structure rather than concrete burden. Importers should track the prong mix that holds the action up, not the rate that sits on top of it.
The determination treats six issue areas, and it does not build them the same way. The digital trade finding points to identifiable United States firms and identifiable enforcement events. The preferential tariff finding points to measurable tariff differentials and import values. The ethanol finding points to a decline in a specific United States export line over a defined period. The intellectual property finding points to enforcement gaps against counterfeit goods. The illegal deforestation finding points to agricultural and timber products produced on illegally deforested land and to alleged lost revenues and sales for United States producers. On a litigation read, each of those findings gives USTR a concrete record hook, because it ties the practice to something a court can weigh as a burden on United States commerce.
The anti-corruption finding is different in kind. It draws its most concrete factual support from OECD concerns about Brazil's foreign bribery enforcement and from a 2023 decision by Brazilian Supreme Court Justice Dias Toffoli setting aside evidence tied to the Operation Car Wash cases. The determination records that Brazil's own prosecutors challenged that decision and that the challenge remains pending. All of that is documented. None of it, on its own, is a burden on United States commerce. The burden has to be supplied separately, and that is where the finding thins out. Relative to the other five findings, the determination gives this anti-corruption nexus the thinnest commerce connection. USTR does not make that comparison itself.
The hook and the commerce burden do different work
It would be wrong to argue that anti-corruption enforcement cannot support a Section 301 action at all. It can. When Congress amended the statute in 2016, it wrote a list of conduct that counts as unreasonable into 19 U.S.C. 2411(d)(3)(B)(iv), and that list includes a persistent pattern under which a foreign government fails to effectively enforce commitments under agreements to which that country and the United States are both parties, with anti-corruption named alongside labor, the environment, and intellectual property. The determination places the anti-corruption prong inside an OECD anti-bribery enforcement frame rather than a bare characterization of Brazilian politics.
That hook answers the threshold objection that USTR is using a trade statute for a subject Congress never put into the statute. It does not answer the burden requirement. The statutory hook and the commerce burden do different work. Section 301 treats failures to enforce anti-corruption commitments as a possible unreasonable practice. The discretionary action provision at 19 U.S.C. 2411(b) still requires USTR to show that the practice burdens or restricts United States commerce. Clause (iv) supplies the first step. The record still has to supply the second, and for this prong the record supplies it in general terms.
The nexus, not the hook, is where this prong is thin
USTR's stated commerce nexus is competitive asymmetry. It says corrupt companies may operate in Brazil with impunity while United States companies face significant requirements and potential liability for foreign corrupt practices and are disadvantaged in seeking trade and investment opportunities in Brazil. That is a coherent theory. It is not, as written, tied to a named firm, a lost contract, a specific investment that was blocked, or a quantified compliance cost.
The generality matters more here than it would elsewhere because the statute defines commerce broadly. Under 19 U.S.C. 2411(d)(1), commerce is not limited to goods. It reaches services associated with international trade and foreign direct investment by United States persons with implications for trade in goods or services. That breadth cuts in USTR's favor at the threshold, because the anti-corruption theory does not fail simply for lack of a goods transaction. USTR could ground the burden in a services restriction or an investment disadvantage. The problem is that the record, as reflected in the determination, does not do that work. It describes a structural disadvantage and stops.
That is the exposure. The APA problem is whether the explanation USTR gave connects the anti-corruption finding to a statutory burden on United States commerce. If USTR rested on a generalized competitive asymmetry without connecting it to a specific burden the broad commerce definition would have allowed it to show, the nexus becomes the most attackable part of the action under the arbitrary and capricious standard in 5 U.S.C. 706. The strength of the theory in the abstract does not cure a thin record in the particular.
The strongest challenge stays inside the record
The formal Section 301 record frames the anti-corruption issue as under-enforcement and lack of transparency, and as criticism of rulings that set aside convictions. Read on its own terms, the prong is an under-enforcement theory, not a complaint about the prosecution of any particular figure.
That framing is what makes the strongest challenge a record-based nexus challenge rather than an argument that depends on external political statements. A pretext argument has to reach outside the record. A nexus challenge stays inside it, and it does not need to prove motive to win. It only needs to show that the determination described a structural disadvantage without connecting it to a burden the statute recognizes.
The better vulnerability is reasoned explanation, not equivalence
It is tempting to argue that a single 25 percent rate is unlawful because it is not apportioned across the six prongs, so that the weakness of one prong infects the whole rate. That argument reaches too far, and the statute is the reason. The equivalence language that requires an action to match the value of the burden lives in the mandatory action provision at 19 U.S.C. 2411(a)(3). This is a discretionary action under 2411(b), where the command is to take all appropriate and feasible action, and 2411(c)(3) lets USTR act against goods or an economic sector without regard to whether those goods or that sector were involved in the practice at issue. A challenge framed as statutory equivalence would likely lose.
The better vulnerability is reasoned explanation. The better challenge is not that Section 301 requires mathematical apportionment across six findings. It is that a single blended rate needs a reasoned explanation if one finding supplies a thin commerce nexus and the final action still relies on that finding. Broad remedial latitude is not the same as freedom from explanation. That is a remand risk on the explanation, not a rate defect that voids the action on its face.
The exclusion annex narrows the effective base
The remedy is narrower than a flat 25 percent on all Brazilian trade. The determination pairs the rate with an annex of exclusions built on supply chain and availability logic rather than on any of the six findings. It excludes goods that cannot be sourced domestically, goods whose taxation would cause broad economic disruption, goods not available in sufficient quantity from the United States or alternative suppliers, and goods for which added tariffs would not contribute substantially to eliminating the practices at issue. It separately carves out articles already covered by Section 232 measures and listed civil aircraft lines.
The practical exposure turns on Harmonized Tariff Schedule coverage, not the headline rate alone. The effective base is narrower than the headline, which widens the gap between what the action nominally targets and what it actually taxes, and that gap is useful material for a challenge to whether the chosen remedy is a reasoned response to the practices the determination identifies. The precise list of excluded subheadings and any characterization of Brazil's largest export categories should be confirmed against the final annex and trade data before it is relied on.
The theory is thinly tested, not unprecedented
The safer formulation is that the theory is thinly tested. Using a foreign enforcement and judicial pattern as the spine of a Section 301 tariff is not something the statute forbids, because the statute now contains an anti-corruption hook. The open question is applied, whether a foreign enforcement pattern can carry a tariff remedy once the commerce burden is contested. Litigation on that precise question is scarce, and any claim that it has never been done would need a full Section 301 case-history audit before it could be stated as fact.
Two points frame it without making a factual claim about Brazil. The review question is whether USTR explained the final action well enough for the record to survive arbitrary and capricious review under 5 U.S.C. 706. Other Section 301 tracks show USTR testing nontraditional issue areas, but that does not answer the Brazil question, which is whether a foreign enforcement pattern can support a tariff remedy once the commerce burden is contested. The determination itself shows USTR treading carefully around a foreign court, declining in the digital trade prong to make an actionability finding as to a specific Brazilian Supreme Court decision. That caution is a signal that USTR sees the same exposure.
Where Section 301 stands after the IEEPA ruling
The reason this action exists in its current form is that the Supreme Court held in Learning Resources, Inc. v. Trump that IEEPA does not authorize the President to impose tariffs. That removed IEEPA as the asserted authority for the emergency-tariff track and pushed leverage back onto the trade statutes. It does not directly control Section 301, which carries express duties language and a record-building process of its own, and that is what separates Section 301 from the IEEPA reading the Court rejected.
The risk here is therefore action-specific explanation rather than authority-wide invalidity. Durability of the authority is not the same as durability of this action. The framework can be sound while a particular finding inside it is exposed. That is the situation here, and it is why the analysis stays on the anti-corruption prong rather than on Section 301 as a whole.
Why this is new
The official record presents one proposed tariff action built on six findings. The analytical move here is to disaggregate those findings and ask which ones carry the commerce-burden explanation. A Section 301 action can rest on several findings at once. A finding that is thin on the commerce nexus does not automatically void the action, but it can create a reasoned-explanation and remand question, so the durable question is not whether the action as a whole looks strong. It is whether the action still stands if the thinnest finding is discounted, and whether a single blended remedy still reads as explained once that happens.
Applied to Brazil, that test isolates one prong. Ask, finding by finding, whether the determination connects the practice to a burden the statute recognizes. Five of the six answer with something specific. The sixth answers with a structural description. That comparison is the point, and it turns on the record rather than the politics around the action.
What importers and Brazil-exposed firms should do
Map Harmonized Tariff Schedule coverage against the annex first, and preserve entry records. The exclusion list is built on supply chain logic that has nothing to do with the six findings, so a given subheading may already be outside the base regardless of how the legal fight turns out. Identify whether your exposure depends on the anti-corruption finding or on other findings with stronger record ties, because that is what determines how far the July hearing and the final action can move your position.
The proposed rate is the starting point, not the durable fact. What is not fixed is which findings survive contact with the hearing and, if it comes to it, with a court. Preserve entry records and track liquidation status, because any later refund posture will turn on the procedural status of the entries under the customs statutes on liquidation and protest as well as on the outcome of any challenge.
What would change the calculus
Three things move this materially. First, the final action. If USTR drops or narrows the anti-corruption prong after the hearing, the nexus risk identified here largely disappears, though the final rate and annex would still need their own explanation. If it keeps the prong and sets an effective date, the litigation window opens. Second, the hearing record. The gap to watch is whether USTR uses the July hearing and any posted transcript or final-action explanation to add specific commerce-burden evidence behind the anti-corruption prong, since that is the thin spot and the broad statutory definition of commerce gives it room to try. Third, any judicial signal on how far the Learning Resources reasoning reaches, though the express delegation behind Section 301 makes a direct read across unlikely.
Caveats
This is a proposed action, not a final one. USTR can change the findings it relies on, the annex, the effective date, or the 25 percent rate before it takes final responsive action, so the anti-corruption analysis here should be read against the final action if USTR narrows or drops that prong.
Two points rest on records that are not yet fixed. The precise count of excluded subheadings and aircraft lines depends on the final annex, which can change between proposal and final action. And the available case history does not identify a prior Section 301 action that rested on a foreign judicial or prosecutorial pattern, although the review is not an exhaustive negative search.
The public hearing runs on July 6 and July 7 2026, and the responsive-action deadline is July 15 2026, so the determination stage, the rate, and the effective date can still move.