Lead Opinion
delivered the opinion of the Court.
Under Cage v. Louisiana,
I
During a fight with his estranged girlfriend in March 1975, petitioner Melvin Tyler shot and killed their 20-day-old daughter. A jury found Tyler guilty of second-degree murder, and his conviction was affirmed on appeal. After sentencing, Tyler assiduously sought postconviction relief. By 1986, he had filed five state petitions, all of which were denied. See State ex rel. Tyler v. Blackburn,
In early 1997, Tyler returned to federal court. Seeking to pursue his Cage claim, Tyler moved the United States
The District Court proceeded to the merits of Tyler’s claim and held that, although Cage should apply retroactively, App. 5-7 (citing Humphrey v. Cain,
The Court of Appeals affirmed. Judgt. order reported at
The Courts of Appeals are divided on the question whether Cage was “made retroactive to cases on collateral review by the Supreme Court,” as required by 28 U. S. C. § 2244(b)(2)(A). Compare Rodriguez v. Superintendent,
h — <
AEDPA greatly restricts the power of federal courts to award relief to state prisoners who file second or successive habeas corpus applications. If the prisoner asserts a claim that he has already presented in a previous federal ha-beas petition, the claim must be dismissed in all cases. § 2244(b)(1). And if the prisoner asserts a claim that was not presented in a previous petition, the claim must be dismissed unless it falls within one of two narrow exceptions. One of these exceptions is for claims predicated on newly
It is the latter exception that concerns us today. Specifically, § 2244(b)(2)(A) covers claims that “rel[y] on a new rule of constitutional law, made retroactive to cases on collateral review by the Supreme Court, that was previously unavailable.” This provision establishes three prerequisites to obtaining relief in a second or successive petition: First, the rule on which the claim relies must be a “new rule” of constitutional law; second, the rule must have been “made retroactive to cases on collateral review by the Supreme Court”; and third, the claim must have been “previously unavailable.” In this case, the parties ask us to interpret only the second requirement; respondent does not dispute that Cage created a “new rule” that was “previously unavailable.” Based on the plain meaning of the text read as a whole, we conclude that “made” means “held” and, thus, the requirement is satisfied only if this Court has held that the new rule is retroactively applicable to cases on collateral review.
A
As commonly defined, “made” has several alternative meanings, none of which is entirely free from ambiguity. See, e. g., Webster’s Ninth New Collegiate Dictionary 718-719 (1991) (defining “to make” as “to cause to happen,” “to cause to exist, occur or appear,” “to lay out and construct,” and “to cause to act in a certain way”). Out of context, it may thus be unclear which meaning should apply in § 2244(b)(2)(A), and how the term should be understood. We do not, however, construe the meaning of statutory terms in a vacuum. Rather, we interpret the words “in their context and with a view to their place in the overall statutory scheme.” Davis v. Michigan Dept. of Treasury,
The only way the Supreme Court can, by itself, “lay out and construct” a rule’s retroactive effect, or “cause” that effect “to exist, occur, or appear,” is through a holding. The Supreme Court does not “ma[k]e” a rule retroactive when it merely , establishes principles of retroactivity and leaves the application of those principles to lower courts. In such an event, any legal conclusion that is derived from the principles is developed by the lower court (or perhaps by a combination of courts), not by the Supreme Court.
We further note that our interpretation is necessary for the proper implementation of the collateral review structure created by AEDPA. Under the statute, before a state prisoner may file a second or successive habeas application, he “shall move in the appropriate court of appeals for an order authorizing the district court to consider the application.” § 2244(b)(3)(A). The court of appeals must make a decision on the application within 30 days. § 2244(b)(3)(D). In this limited time, the court of appeals must determine whether the application “makes a prima facie showing that [it] satisfies the [second habeas standard].” § 2244(b)(3)(C). It is unlikely that a court of appeals could make such a determination in the allotted time if it had to do more than simply rely on Supreme Court holdings on retroactivity. The stringent time limit thus suggests that the courts of appeals do not have to engage in the difficult legal analysis that can be required to determine questions of retroactivity in the first instance.
B
Because “made” means “held” for purposes of § 2244(b)(2)(A), it is clear that the Cage rule has not been “made retroactive to cases on collateral review by the Supreme Court.” Cage itself does not hold that it is retroac
Tyler argues, however, that a subsequent case, Sullivan v. Louisiana,
According to Tyler, the reasoning of Sullivan demonstrates that the Cage rule satisfies both prongs of this Teague exception. First, Tyler notes, Sullivan repeatedly emphasized that a Cage error fundamentally undermines the reliability of a trial’s outcome. And second, Tyler contends, the central point of Sullivan is that a Cage error deprives a defendant of a bedrock element of procedural fairness: the right to have the jury make the determination of guilt beyond a reasonable doubt. Tyler’s arguments fail to persuade, how
Justice Breyer observes that this Court can make a rule retroactive over the course of two cases. See post, at 672-673 (dissenting opinion). We do not disagree that, with the right combination of holdings, the Court could do this. But even so, the Court has not made Cage retroactive. Multiple cases can render a new rule retroactive only if the holdings in those cases necessarily dictate retroactivity of the new rule. The only holding in Sullivan is that a Cage error is structural error. There is no second case that held that all structural-error rules apply retroactively or that all structural-error rules fit within the second Teague exception. The standard for determining whether an error is structural, see generally Arizona v. Fulminante,
Ill
Finally, Tyler suggests that, if Cage has not been made retroactive to cases on collateral review, we should make it retroactive today. We disagree. Because Tyler’s habeas application was his second, the District Court was required to dismiss it unless Tyler showed that this Court already had made Cage retroactive. § 2244(b)(4) (“A district court shall dismiss any claim presented in a second or successive application that the court of appeals has authorized to be filed unless the applicant shows that the claim satisfies the requirements of this section”); § 2244(b)(2)(A) (“A claim presented in a second or successive habeas corpus application under section 2254 that was not presented in a prior application shall be dismissed unless . . . the applicant shows that
* * *
The judgment of the Court of Appeals is affirmed.
It is so ordered.
Notes
In Cage, this Court observed that a reasonable juror “could have” interpreted the instruction at issue to permit a finding of guilt without the requisite proof
AEDPA requires that, “[b]efore a second or successive application . .. is filed in the district court, the applicant shall move in the appropriate court of appeals for an order authorizing the district court to consider the application.” 28 U. S. C. § 2244(b)(3)(A) (1994 ed., Supp. V).
This requirement differs from the one that applicants must satisfy in order to obtain permission from a court of appeals to file a second or successive petition. As noted above, a court of appeals may authorize such a filing only if it determines that the applicant makes a “prima facie showing” that the application satisfies the statutory standard. § 2244(b)(3)(C). But to survive dismissal in district court, the applicant must actually “sho[w]” that the claim satisfies the standard.
Similarly, the Supreme Court does not make a rule retroactive through dictum, which is not binding. Cf. Seminole Tribe of Fla. v. Florida,
Tyler argues that defining “made” to mean “held” would create an anomaly: When it is obvious that a rule should be retroactive, the courts of appeals will not be in conflict, and this Court will never decide to hear the ease and will never make the rule retroactive. Thus, Tyler concludes, we should construe § 2244(b)(2)(A) to allow for retroactive application whenever the “principles” of our decisions, as interpreted by the courts of appeals, indicate that retroactivity is appropriate. This argument is flawed, however. First, even if we disagreed with the legislative decision to establish stringent procedural requirements for retroactive application of new rules, we do not have license to question the decision on policy grounds. See Connecticut Nat. Bank v. Germain,
We also reject Tyler’s attempt to find support in our disposition in Adams v. Evatt,
As explained above, the second Teague exception is available only if the new rule “alter[s] our understanding of the bedrock procedural elements” ’ essential to the fairness of a proceeding.” Sawyer v. Smith,
Concurrence Opinion
concurring.
I join the Court’s opinion and write separately to explain more fully the circumstances in which a new rule is “made retroactive to cases on collateral review by the Supreme Court.” 28 U S. C. § 2244(b)(2)(A) (1994 ed., Supp. V).
It is only through the holdings of this Court, as opposed to this Court’s dicta and as opposed to the decisions of any other court, that a new rule is “made retroactive ... by the Supreme Court” within the meaning of § 2244(b)(2)(A). See ante, at 663; cf. Williams v. Taylor, 529 U. S. 362, 412 (2000). The clearest instance, of course, in which we can be said to have “made” a new rule retroactive is wheré we expressly have held the new rule to be retroactive in a. case on collateral review and applied the rule to that case. But, as the Court recognizes, a single case that expressly holds a rule to be retroactive is not a sine qua non for the satisfaction of this statutory provision. Ante, at 666. This Court instead may “ma[k]e” a new rule retroactive through multiple holdings that logically dictate the retroactivity of the new rule. Ibid. To apply the syllogistic relationship described by Justice Breyer, post, at 672-673 (dissenting opinion), if we hold in Case One that a particular type of rule applies retroactively to cases on collateral review and hold in Case Two
The relationship between the conclusion that a new rule is retroactive and the holdings that “ma[k]e” this rule retroactive, however, must be strictly logical — i e., the holdings must dictate the conclusion and not merely provide principles from which one may conclude that the rule applies retroactively. As the Court observes, “[t]he Supreme Court does not ‘ma[k]e’ a rule retroactive when it merely establishes principles of retroactivity and leaves the application of those principles to lower courts.” Ante, at 663. The Court instead can be said to have “made” a rule retroactive within the meaning of § 2244(b)(2)(A) only where the Court’s holdings logically permit no other conclusion than that the rule is retroactive.
It is relatively easy to demonstrate the required logical relationship with respect to the first exception articulated in Teague v. Lane,
The matter is less straightforward with respect to the second Teague exception, which is reserved for “watershed
Dissenting Opinion
with Ayhom Justice Stevens, Justice Souter, and Justice Ginsburg join, dissenting.
In Cage v. Louisiana,
The Court made Cage retroactive in two cases taken together. Case One is Teague v. Lane,
Case Two is Sullivan v. Louisiana,
, To reason as the Court reasoned in Sullivan is to hold (in Teague’s language) (1) that infringement of the Cage rule “seriously diminishes] the likelihood of obtaining an accurate
Consequently, Sullivan, in holding that a Cage violation can never be harmless because it leaves the defendant with no jury verdict known to the Sixth Amendment, also holds that Cage falls within Teague's “watershed” exception. The matter is one of logic. If Case One holds that all men are
The majority says that Sullivan’s only “holding” is that Cage error is structural, and that this “holding” does not dictate the “watershed” nature of the Cage rule. See ante, at 665-666. ' But the majority fails to identify a meaningful difference between the definition of a watershed rule under Teague and the standard that we have articulated in the handful of instances in which we have held errors structural, namely, that structural errors deprive a defendant of a “‘basic protectio[n]’” without which a “‘trial cannot reliably serve its function as a vehicle for determination of guilt or innocence’” to the point where “‘no criminal punishment may be regarded as fundamentally fair.’ ” Arizona v. Fulminante,
Of course, as the majority points out, identifying an error as structural need not “alter our understanding of th[e] fun
Insofar as the majority means to suggest that a rule may be sufficiently “new” that it does not apply retroactively but not “new enough” to qualify for the watershed exception, I note only that the cases establishing this exception suggest no such requirement. Rather than focus on the “degree of newness” of a new rule, these decisions. emphasize that watershed rules are those that form part of the fundamental requirements of due process. See Teague,
Nor does the majority explain why the reasoning that was necessary to our holding in Sullivan (and is therefore binding upon all courts) lacks enough legal force to “make” the Cage rule retroactive. Cf. Seminole Tribe of Fla. v. Florida,
I agree with Justice O’Connor — as does a majority of the Court — when (in describing a different Teague exception) she says that “[w]hen the Court holds as a new rule in a subsequent case that a particular species of primary, private individual conduct is beyond the power, of the criminal lawmaking authority to proscribe, it necessarily follows that this Court has ‘made’ that new rule retroactive to cases on collateral review.” Ante, at 669 (concurring opinion). But I do
I would add two further points. First, nothing in the statute’s purpose favors, let alone requires, the majority’s conclusion. That purpose, as far as I can surmise, is to bar successive petitions when lower courts, but not the Supreme Court, have held a rule not to be “new” under Teague because dictated by their own precedent, cf. Dyer v. Calderon,
Even this complex route will remain open only if the relevant statute of limitations is interpreted to permit its 1-year filing period to run from the time that this Court has “made” a new rule retroactive, not from the time it initially recognized that new right. See 28 U. S. C. § 2244(d)(1)(C) (1994 ed., Supp. V) (limitations period runs from “the date on which the constitutional right asserted was initially recognized by the Supreme Court, if the right has been newly recognized by the Supreme Court and made retroactively applicable to cases on collateral review”). Otherwise, the Court’s approach will generate not only complexity, along with its attendant risk of confusion, but also serious additional unfairness.
I do not understand the basis for the Court’s approach. I fear its consequences. For these reasons, with respect, I dissent.
